Oleg Kalnichevski wrote: > On Sat, 2008-01-19 at 09:33 -0800, Sam Berlin wrote: >> It almost certainly would work, however HttpClient would then be >> broken (as far as URI parsing goes) for everyone else. As others have >> pointed out (and as Tim explained to me in sad detail), URI is just >> basically broken when it comes to using it with the multi-arg >> constructors. It's flat-out impossible to recreate a URI with the >> multi-arg constructors and have it point to the correct resource. > > What would be your suggestion on dealing with the issue? Is there anyway > we could avoid rewriting the whole URI class and leverage functionality > already available in the JRE?
I don't know by heart where we are creating URIs. If path escaping is the problem, maybe we can use some workaround like: URI base = new URI(scheme, hostport, null); URI full = base.resolve(pathonly); // maps to single-arg constructor cheers, Roland --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
