Hi, On Sat, 2005-10-08 at 17:10 +0200, Robert Schuster wrote: > Furthermore: Not accepting superfluous slashes would not help the application > in > which I found this problem.
I agree. We should be liberal in what we accept.
> b) Changing URL in a way that toString() returns the right value (that means
> not
> swallowing the two slashes) would introduce an incompatibility with the JDK.
>
> At last I find it better to fix URL's toString() because it seems so
> strikingly
> wrong for me that in this scenario:
>
> u = new URL("file:////home/bla");
> u2 = new URL(u.toString());
>
> u and u2 do not resolve the same file.
>
> Any other opinions?
This really looks like a bug.
u and u2 should have equals URL components.
Is there anything in the W3C 'file' URI Scheme Update Project that could
help us decide how to correctly parse "broken" file URLs?
http://offset.skew.org/wiki/URI/File_scheme
Cheers,
Mark
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Classpath-patches mailing list Classpath-patches@gnu.org http://lists.gnu.org/mailman/listinfo/classpath-patches
