Can anyone please tell me if there is a difference between the BASE64-DECODE function of Progress for BASE64_DECODE of PHP and BASE64-ENCODE of Progress for BASE64_ENCODE of PHP?
I'm building an application in Progress copy of another application in PHP using these functions and the result is being different.
Is there any other similar function in BASE64_DECODE's Progress or PHP's BASE64_ENCODE?
I think (and I could be very wrong) PHP might truncate the base64 string into 1or4k chunks, as it sometimes needed for encoding of attachments in email which has some limit.
Is possible can you show us your PHP code. I'm not a PHP developer but I will see if I can revere engineer the PHP code. Don't take offense, but I see from the Progress Community that you have already done this, but you might have missed something.
For us [ProgressTalk.com] we will need to do a code functionally comparison between the PHP code and the ABL.
Is possible can you show us your PHP code. I'm not a PHP developer but I will see if I can revere engineer the PHP code. Don't take offense, but I see from the Progress Community that you have already done this, but you might have missed something.
For us [ProgressTalk.com] we will need to do a code functionally comparison between the PHP code and the ABL.
I put the same doubt in several Progress communities, because I need to solve the problem of using Progress, because there is the function BASE64-DECODE in PHP and Progress and are returning different values. My base is Progress, PHP was the example I have to follow.
Thanks.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.