Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!news.swapon.de!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Stanimir Stamenkov <s7an10@netscape.net>
Newsgroups: comp.lang.java.programmer
Subject: Re: [LONG] java.net.URI encoding weirdness
Date: Tue, 06 May 2014 22:34:25 +0300
Organization: A noiseless patient Spider
Lines: 27
Message-ID: <lkbdg1$4va$1@dont-email.me>
References: <lk82m6$hhi$1@dont-email.me> <lk8n0o$ibf$1@dont-email.me> <lk8u3d$agp$1@dont-email.me> <lk9861$dk5$1@dont-email.me> <lka2s0$kma$1@dont-email.me> <lkb5rt$83i$1@dont-email.me> <lkbctv$dg$1@dont-email.me>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Tue, 6 May 2014 19:34:25 +0000 (UTC)
Injection-Info: mx05.eternal-september.org; posting-host="daaaf033c96883e83e80378381c6380d"; logging-data="5098"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18wG6TWFya/6lFQ97sZeG48"
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26
In-Reply-To: <lkbctv$dg$1@dont-email.me>
X-Face: "@)%Vlap6d%OVYDS}B4YUWE@yUy+^!w/+.q.,c5kjI#+uG?kYP&r/pTjNWgo:g[A,O=AL3/ j&4Le2cau$<e=FPq~GbeZ6DW1Grey[VHn8?ktzvoQtzlg;]&rh8g]CD+_BC7d[gW{Yx&_X*4Q$h&nJ l@t(|4R4:T='&]U#ui+z9OC$.~gJjU93kh:Ojc$Cz0n#I9!~!9ay?E<UlW&5,IFX1*KtA>MYEFst$y y"m]M7tq\S(>[a$x0x8%S
Cancel-Lock: sha1:gGXnirXGv3167/KqXrfq+ZSVZy8=
Xref: csiph.com comp.lang.java.programmer:28402

Tue, 06 May 2014 12:24:44 -0700, /markspace/:

> OK, I think I see what is going on.  Most of your OP was frankly
> wrong, however this one represents an actual bug in the URI parsing:
> [...]
>      // "raw" is user error, omitted.

I was just demonstrating it is impossible to get a correct result 
both ways.

> Oracle should consider replacing it with a ctor that allows the
> query to be parsed correctly:
>
>    public URI( String scheme, String userInfo, String host,
>           int port, String path, String fragment,
>           String[] ... paramValue ) ...
> [...]

It's not just about the query parameters.  It could be the path 
contains percent encoded characters such as / (slash) and ; 
(semicolon) which should not be decoded before being dereferenced 
(like before parsing matrix parameters).

http://tools.ietf.org/html/rfc3986#section-2.4

-- 
Stanimir