Parsing of URL's which contain Windows Path separator

[Chris Hegarty]

Shirish,

Oooh, I'm not sure that any change to URL of this kind would be 
compatible. It may have been desirable to have this kind of behavior 
when URL was being originally created, but it is a legacy class, now 
replaced with URI, and I'm not sure a change like this could be done in 
a way to preserve compatibility with existing code.

-Chris

On 20/08/12 16:04, Shirish Kuncolienkar wrote:
> Any thoughts on the following
>
> It will be good if the one could create relative url from other url
> which is based on windows style path.
> example "hello.html" relative "http://someserver/foo/bar" becomes
> "http://someserver/foo/hello.html"
>
> In the similar way "hello.html"relative to "file:///C:\foo\bar" can be
> resolved to "file:///C:/foo/hello.html"
> currently the URL parser resolves it to "file:////hello.html" (this
> behavior is correct going by the api spec, since windows file separator
> character is considered as a special character)
>