commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ryan Hoegg <rho...@isisnetworks.net>
Subject Re: DO NOT REPLY [Bug 19860] -
Date Wed, 14 May 2003 02:27:20 GMT
Fixed in HEAD I presume?  I think this will impact our usage of it, as 
it will cause interoperability problems with other XML-RPC implementations.

As a release draws near with XML-RPC, I will ping back here to see if we 
can get a bugfix Codec release cut so we are using up-to-date dependencies.

--
Ryan Hoegg
Apache XML-RPC
ISIS Networks
http://www.isisnetworks.net

bugzilla@apache.org wrote:

>DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
>RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
><http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19860>.
>ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
>INSERTED IN THE BUG DATABASE.
>
>http://nagoya.apache.org/bugzilla/show_bug.cgi?id=19860
>
>base64 codec doesnt ignore all illegal chars
>
>tobrien@discursive.com changed:
>
>           What    |Removed                     |Added
>----------------------------------------------------------------------------
>             Status|NEW                         |RESOLVED
>         Resolution|                            |FIXED
>
>
>
>------- Additional Comments From tobrien@discursive.com  2003-05-14 02:22 -------
>I plead guilty.  discard whitespace *used* to discard all non-base64 characters
>which brings the base64 implementation to full Base64 compliance - the problem
>with that was that is made the function isArrayByteBase64() completely useless.
>  Assume that discardWhitespace() removes all non-base64 characters, then it is
>pointless to test the groomed byte array to see if it contains only valid base64
>characters.  This was unconvered with the help of Clover - isArrayByteBase64
>*never* returned false.
>
>The compromise, which I'm about to commit is that we retain discardWhitespace
>for use only from isArrayByteBase64() - If someone needs to test a byte array to
>see if it contains base64 encoded data, we will throw away *all* (most?)
>whitespace and then perform the test.  This leaves a possibility of
>isArrayByteBase64 returning false if a byte array contains characters outside of
>the base64 alphabet.
>
>A new function discardNonBase64 discards all characters outside of the Base64
>alphabet AND brings the implementation up to compliance.  Thank you for pointing
>this out.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message