Re: Semicolon URI encoding and RFC

2011-05-11 Thread Mindaugas Žakšauskas
Christopher Schultz> So, you want to /only/ escape those entities that are /absolutely Christopher Schultz> required/ to be escaped? Yes. Christopher Schultz> I'm not sure anyone really cares what URLs look like, do they? Konstantin Kolinko> readability? nobody reads the HTML source Search engin

Re: Semicolon URI encoding and RFC

2011-05-11 Thread Konstantin Kolinko
2011/5/11 Mindaugas Žakšauskas : > On Tue, May 10, 2011 at 7:31 PM, Christopher Schultz > wrote: >> <..> >> What about http://site/test1%28test2/ >> >> Does that give you "/test1)test2/"? > > Closing bracket is %29 but yes, it does. > >> If so, Tomcat is probably following SOP with regard to stand

Re: Semicolon URI encoding and RFC

2011-05-11 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mindaugas, On 5/11/2011 9:16 AM, Mindaugas Žakšauskas wrote: > On Tue, May 10, 2011 at 7:31 PM, Christopher Schultz > wrote: >> <..> >> What about http://site/test1%28test2/ >> >> Does that give you "/test1)test2/"? > > Closing bracket is %29 but ye

Re: Semicolon URI encoding and RFC

2011-05-11 Thread Mindaugas Žakšauskas
On Tue, May 10, 2011 at 7:31 PM, Christopher Schultz wrote: > <..> > What about http://site/test1%28test2/ > > Does that give you "/test1)test2/"? Closing bracket is %29 but yes, it does. > If so, Tomcat is probably following SOP with regard to standards which > is to be conservative in what you

Re: Semicolon URI encoding and RFC

2011-05-10 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mindaugas, On 5/9/2011 6:32 AM, Mindaugas Žakšauskas wrote: > http://site/test1)test2//test1)test2/ What about http://site/test1%28test2/ Does that give you "/test1)test2/"? If not, something is probably wrong. If so, Tomcat is probabl

Re: Semicolon URI encoding and RFC

2011-05-10 Thread Mindaugas Žakšauskas
Hi, Thanks very much for your answers. Just for a reference, I will sum up what I've managed to get out of this discussion. Please correct me if I am wrong. My problem wasn't charset incompatibility between client and server as it is the same party which produces URLs and consumes them (and yes,

Re: Semicolon URI encoding and RFC

2011-05-09 Thread André Warnier
Caldarale, Charles R wrote: From: André Warnier [mailto:a...@ice-sa.com] Subject: Re: Semicolon URI encoding and RFC The "site" (or hostname) part of the URL is submitted to a different encoding than the path part (/pathąčęė). The path part must be URL- encoded, but for the hos

RE: Semicolon URI encoding and RFC

2011-05-09 Thread Caldarale, Charles R
> From: André Warnier [mailto:a...@ice-sa.com] > Subject: Re: Semicolon URI encoding and RFC > The "site" (or hostname) part of the URL is submitted to a different > encoding than the path part (/pathąčęė). The path part must be URL- > encoded, but for the hostn

Re: Semicolon URI encoding and RFC

2011-05-09 Thread André Warnier
Konstantin Kolinko wrote: .. 2011/5/9 André Warnier : (like a space encoded as a "+", and a "+" encoded as %xy), Andre, one small correction: It sometimes causes confusion, but encoding of space as '+' works only in the query part of the URL. The unambiguous way to encode a space regardless o

Re: Semicolon URI encoding and RFC

2011-05-09 Thread Konstantin Kolinko
2011/5/9 Mindaugas Žakšauskas : > On Mon, May 9, 2011 at 2:03 PM, Konstantin Kolinko > wrote: > <..> >> If ";" is part of the actual path, it must be escaped. >> >> If ";" starts a "path parameter" it must be unescaped. One well-known >> example is ";jsessionid" path parameter. > > Thanks for your

Re: Semicolon URI encoding and RFC

2011-05-09 Thread André Warnier
Hi. This whole question is a pain in the a.. , and I personally do not understand how a million marketing people can be talking of "web 2.0" and "web 3.0", but not have been able to come out with HTTP 2.0 where URLs (and everything else) would be by default Unicode/UTF-8 instead of ASCII and/o

Re: Semicolon URI encoding and RFC

2011-05-09 Thread Mindaugas Žakšauskas
On Mon, May 9, 2011 at 2:03 PM, Konstantin Kolinko wrote: <..> > If ";" is part of the actual path, it must be escaped. > > If ";" starts a "path parameter" it must be unescaped. One well-known > example is ";jsessionid" path parameter. Thanks for your answer. Is this rule is just "de facto" rule

Re: Semicolon URI encoding and RFC

2011-05-09 Thread Konstantin Kolinko
2011/5/9 Mindaugas Žakšauskas : > Hi, > > I was trying to read RFCs 3986 and 2396 to understand some subtleties > about URI encoding. > > In particular I am interested about whether semicolon (;) needs to be > percent escaped as, e.g. http://site/some;path VS > http://site/some%3Bpath when outputti

Semicolon URI encoding and RFC

2011-05-09 Thread Mindaugas Žakšauskas
Hi, I was trying to read RFCs 3986 and 2396 to understand some subtleties about URI encoding. In particular I am interested about whether semicolon (;) needs to be percent escaped as, e.g. http://site/some;path VS http://site/some%3Bpath when outputting e.g. HTML href element. Just for interest,