On Fri, 8 Aug 2003, David Byron wrote:

> I think that leaves us with two kinds of paths that "should" work for
> Windows:
>
> a. paths relative to the root of the current drive
> b. absolute paths that start with a drive letter and a colon (or pipe)

I agree. I think that fine URLs that are following the spec AND that work in
browsers should work.

> And one more that my testing below shows happens to work, but I haven't seen
> discussed here:
>
> c. paths relative to the current directory of a drive. See tests 9-12
> below.

All those are not really using the correct URL syntax as defined in RFC1738.

> The patch is attached. It's basically the one that Dan Fandrich sent.

Thanks. I've applied and committed with a minor fix: since you increase the
path pointer, we need to be careful to always free() to original pointer
before the increment.

-- 
 Daniel Stenberg -- curl: been grokking URLs since 1998
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01