At 02:51 AM 6/3/2002, Paul replied:
Cliff Woolley wrote: > > On Mon, 3 Jun 2002, Paul Marculescu wrote: > > > I made a little patch for apr-util's apr_uri.c to handle win32 absolute > > paths under file:// schema. > > I'll admit it strikes me as a bit odd to be supporting platform-specific > forms of _uniform_ resource identifiers. :-) Is this a > standards-recognized form or is it just one that Microsoft made up? If > it's valid under the standard, then I suppose it makes sense to support > it.
:) I think you are right, but suppose you're on a Win32 platform and you want to specify this path: D:/test in a file url. According to the standards, it will be file:///D:/test Right?
The apr_uri_parse() function generates the path /D:/test from this URI. This is where I got a little confused, since rfc's said:
A file URL takes the form: file://<host>/<path> where <host> is the fully qualified domain name of the system on which the <path> is accessible, and <path> is a hierarchical directory path of the form <directory>/<directory>/.../<name>.
so why is the '/' after the host included in the path?
It is... ever used Netscape? They choose to follow the rfc (while encoding
the d: as d|... e.g. file:///d|/foo ... and unless that second colon is ambigious,
I'd suggest we support either : or | for consistency [the "|" is entirely invalid in
win32 paths, as are ">" and "<"].
