You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by bu...@apache.org on 2002/09/28 01:43:57 UTC
DO NOT REPLY [Bug 9931] -
Base64 decoder chokes on a whitespace
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=9931>.
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=9931
Base64 decoder chokes on a whitespace
dlr@finemaltcoding.com changed:
What |Removed |Added
----------------------------------------------------------------------------
URL| |http://cvs.apache.org/viewcv
| |s/xml-
| |rpc/src/test/org/apache/xmlr
| |pc/Base64Test.java?rev=1&con
| |tent-type=text/vnd.viewcvs-
| |markup
------- Additional Comments From dlr@finemaltcoding.com 2002-09-27 23:43 -------
Hmm. I just wrote a very simple test case for the Base64 implementation which
Jon nabbed from Tomcat (I found the attached one a bit too abstract to follow
easily). I was unable to reproduce the failure, even by appending whitespace to
the end of the line (you can try it out yourself with `ant test`):
<http://cvs.apache.org/viewcvs/xml-rpc/src/test/org/apache/xmlrpc/Base64Test.java?rev=1&content-type=text/vnd.viewcvs-markup>
Vjekoslav, can you tell me what the correct method of handling whitespace in
base64-encoded data is? The closest thing that I found to a RFC on that is
<http://www.zvon.org/tmRFC/RFC3156/Output/chapter3.html> -- it recommends
stripping trailing whitespace. Is this what Apache's implementation should be
doing? Or should it collapse all lines of base64-encoded data together, then
decode that?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>