commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 31961] New: - Support of Base 64 Encoding with URL and Filename Safe Alphabet
Date Fri, 29 Oct 2004 13:48:59 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=31961>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=31961

Support of Base 64 Encoding with URL and Filename Safe Alphabet

           Summary: Support of Base 64 Encoding with URL and Filename Safe
                    Alphabet
           Product: Commons
           Version: unspecified
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Enhancement
          Priority: Other
         Component: Codec
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: agilbert@taleo.com


The default Base64 alphabet is not safe to use for URL query parameters since 
the '+' character is converted to a ' ' (space) when the parameter value is 
retrieved from the request (ServeltRequest.getParameter(String) 
and .getParameterValues(String)).

It is possible to post-process the result of Base64.encodeBase64 but I would 
rather prefer to specify an alternate alphabet or call another method.

Refer to http://www.ietf.org/rfc/rfc3548.txt section 4 for more information.

Regards,
Alain Gilbert

---------------------------------------------------------------------
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