commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim O\'Brien <>
Subject Changing the Base64 Alphabet for Filename and URL safety
Date Sat, 07 Jan 2006 20:34:48 GMT

Old bug, but the problem is still relevant.  Essentially, if you've ever tried
to use Base64 to encode anything meant for a URL, you've probably run into the
fact that Base64 includes "+" which tends to throw a spanner in the works.  One
way to get around this is to just post process the result and replace the
offending character, but the RFC suggests an alternate alphabet. see section 4

I think this merits some work, so I'm going to take a stab making base64Alphabet
and lookUpBase64Alphabet instance variables instead of being static variables
initialized in a (eek) static block.

Of course, this should be done without changing the released contract.

Tim O'Brien

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message