[
https://issues.apache.org/jira/browse/CODEC-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12781297#action_12781297
]
Julius Davies commented on CODEC-91:
------------------------------------
FYI: there are two additional changes to the decoding behaviour (as well as
what you've identified here in CODEC-91):
1. Ability to decode even when == is missing (at EOF):
https://issues.apache.org/jira/browse/CODEC-75?focusedCommentId=12712517&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12712517
2. URL-Safe characters are now auto-decoded: CODEC-75
I think these were the only three "on purpose" changes to base64 decoding in
1.4.
> Handling of embedded padding in base64 encoded data changed in 1.4
> ------------------------------------------------------------------
>
> Key: CODEC-91
> URL: https://issues.apache.org/jira/browse/CODEC-91
> Project: Commons Codec
> Issue Type: Bug
> Affects Versions: 1.4
> Reporter: Chris Pimlott
>
> 1.4 changed the way that embedded padding characters (i.e. "=") were handled
> when decoding base64 data. Previously, the decoder ignored them and decoded
> all the data. Now it stops upon encountering the first padding byte. This
> breaks compatibility with previous versions.
> For example, in 1.4,
> b64.decode("Y29tbW9ucwo=".getBytes());
> gives the same result as
> b64.decode("Y29tbW9ucwo=Y29tbW9ucwo=".getBytes());
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
