You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Jonas <ba...@gmail.com> on 2009/03/13 09:28:46 UTC
Base64UrlSafe violating RFC 3548?
Hi,
I recently stumbled across Base64UrlSafe, which claims
'Provides Base64 encoding and decoding with URL and filename safe
alphabet as defined by RFC 3548, section 4.'
In the mentioned section of the RFC [1], they use the '-' character
for value 62 and '_' for value 63.
Strangely, Base64UrlSafe uses '*' for 62 and '-' for 63. Is there any
particular reason why it
doesn't follow the RFC?
Cheers,
Jonas
[1] http://www.faqs.org/rfcs/rfc3548.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Base64UrlSafe violating RFC 3548?
Posted by Jonas <ba...@gmail.com>.
https://issues.apache.org/jira/browse/WICKET-2171
On Fri, Mar 13, 2009 at 3:45 PM, Igor Vaynberg <ig...@gmail.com> wrote:
> feel free to file a bug report.
>
> -igor
>
> On Fri, Mar 13, 2009 at 1:28 AM, Jonas <ba...@gmail.com> wrote:
>> Hi,
>>
>> I recently stumbled across Base64UrlSafe, which claims
>> 'Provides Base64 encoding and decoding with URL and filename safe
>> alphabet as defined by RFC 3548, section 4.'
>> In the mentioned section of the RFC [1], they use the '-' character
>> for value 62 and '_' for value 63.
>> Strangely, Base64UrlSafe uses '*' for 62 and '-' for 63. Is there any
>> particular reason why it
>> doesn't follow the RFC?
>>
>> Cheers,
>> Jonas
>>
>> [1] http://www.faqs.org/rfcs/rfc3548.html
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
>> For additional commands, e-mail: users-help@wicket.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: Base64UrlSafe violating RFC 3548?
Posted by Igor Vaynberg <ig...@gmail.com>.
feel free to file a bug report.
-igor
On Fri, Mar 13, 2009 at 1:28 AM, Jonas <ba...@gmail.com> wrote:
> Hi,
>
> I recently stumbled across Base64UrlSafe, which claims
> 'Provides Base64 encoding and decoding with URL and filename safe
> alphabet as defined by RFC 3548, section 4.'
> In the mentioned section of the RFC [1], they use the '-' character
> for value 62 and '_' for value 63.
> Strangely, Base64UrlSafe uses '*' for 62 and '-' for 63. Is there any
> particular reason why it
> doesn't follow the RFC?
>
> Cheers,
> Jonas
>
> [1] http://www.faqs.org/rfcs/rfc3548.html
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org