You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@wicket.apache.org by Sven Meier <sv...@meiers.net> on 2012/02/23 22:20:49 UTC

UrlEncoder and at-sign @

Hi all,

apparently UrlEncoder doesn't encode the at-sign @, line #189:

         dontNeedEncoding.set('@');

The comment copied from java.net.URLEncoder states however:
          As a last note, Intenet Explorer does not encode the "@" 
character which is clearly not
          unreserved according to the RFC. We are being consistent with 
the RFC in this matter, as
          is Netscape.

So if I understand this correctly, the at-sign @ should be encoded. A 
short google search seems to support this position (although there is 
information claiming the opposite).

Anyone knows why it isn't currently? I'm having problem encoding a 
redirect from Wicket to an external url.

Thanks
Sven

Re: UrlEncoder and at-sign @

Posted by Sven Meier <sv...@meiers.net>.
Hi Dan,

actually I've reread the current URI specification 
(http://tools.ietf.org/html/rfc3986) and "@" *is* allowed in path and query.

I've had problems with reading a request from an external site, which 
insists on sending encoded "@"s. I solved the problem by handling the 
request in a custom wicket resource.

Sven

On 03/07/2012 08:26 PM, Dan Retzlaff wrote:
> Sven, did you resolve this? I encountered a related issue with ":" in path
> segments, but "@" seems to work in the tests I did.
> https://issues.apache.org/jira/browse/WICKET-4442
>
> Dan
>
> On Thu, Feb 23, 2012 at 1:20 PM, Sven Meier<sv...@meiers.net>  wrote:
>
>> Hi all,
>>
>> apparently UrlEncoder doesn't encode the at-sign @, line #189:
>>
>>         dontNeedEncoding.set('@');
>>
>> The comment copied from java.net.URLEncoder states however:
>>          As a last note, Intenet Explorer does not encode the "@" character
>> which is clearly not
>>          unreserved according to the RFC. We are being consistent with the
>> RFC in this matter, as
>>          is Netscape.
>>
>> So if I understand this correctly, the at-sign @ should be encoded. A
>> short google search seems to support this position (although there is
>> information claiming the opposite).
>>
>> Anyone knows why it isn't currently? I'm having problem encoding a
>> redirect from Wicket to an external url.
>>
>> Thanks
>> Sven
>>


Re: UrlEncoder and at-sign @

Posted by Dan Retzlaff <dr...@gmail.com>.
Sven, did you resolve this? I encountered a related issue with ":" in path
segments, but "@" seems to work in the tests I did.
https://issues.apache.org/jira/browse/WICKET-4442

Dan

On Thu, Feb 23, 2012 at 1:20 PM, Sven Meier <sv...@meiers.net> wrote:

> Hi all,
>
> apparently UrlEncoder doesn't encode the at-sign @, line #189:
>
>        dontNeedEncoding.set('@');
>
> The comment copied from java.net.URLEncoder states however:
>         As a last note, Intenet Explorer does not encode the "@" character
> which is clearly not
>         unreserved according to the RFC. We are being consistent with the
> RFC in this matter, as
>         is Netscape.
>
> So if I understand this correctly, the at-sign @ should be encoded. A
> short google search seems to support this position (although there is
> information claiming the opposite).
>
> Anyone knows why it isn't currently? I'm having problem encoding a
> redirect from Wicket to an external url.
>
> Thanks
> Sven
>