|
URI::file not RFC 1738 compliant?: msg#00003lang.perl.modules.lwp
As far as I can tell, RFC 1738, section 3.10, as well as the BNF in section 5 explicitly say that file: URI must have two forward slashes before the optional hostname, followed by another forward slash, and then the path. However: $ perl -MURI::file -e 'print URI::file->new_abs("/foo"), "\n"' file:/foo I would have expected "file:///foo". These "one-slash" file: URIs cause various interoperability problems here and there with applications or other libraries that require strict RFC compliance. For example, XML::LibXML::SAX seems to treat "file:/foo" as a literal relative path from the current directory (ie. "$PWD/file:/foo"), whereas "file:///foo" works with it as expected. Would it be possible to have this fixed in URI? |
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: is_success() returning tru even though server was down: 00003, James Cloos |
|---|---|
| Next by Date: | Re: URI::file not RFC 1738 compliant?: 00003, Gisle Aas |
| Previous by Thread: | is_success() returning tru even though server was downi: 00003, James Cloos |
| Next by Thread: | Re: URI::file not RFC 1738 compliant?: 00003, Gisle Aas |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |