commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Pimlott (JIRA)" <>
Subject [jira] Commented: (CODEC-91) Handling of embedded padding in base64 encoded data changed in 1.4
Date Mon, 23 Nov 2009 16:36:39 GMT


Chris Pimlott commented on CODEC-91:

It's not clear to me if the old behavior was strictly a bug, given the "may".  RFC4648 states:

   Furthermore, such specifications MAY ignore the pad
   character, "=", treating it as non-alphabet data, if it is present
   before the end of the encoded data.

It sounds like either way (ignoring or stopping) of treating the embedded "=" is acceptable.

At the very least, the change in behavior should have been made clear in the release notes
and in the javadoc.  An option to restore the previous behavior would be appreciated as well.

> Handling of embedded padding in base64 encoded data changed in 1.4
> ------------------------------------------------------------------
>                 Key: CODEC-91
>                 URL:
>             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.

View raw message