Re: https:/ and http:/ using relative URLs to switch between secure and non-secure

>(b) I believe this request was considered and declined during the
>development of the URI spec, RFC2396, though I don't have
>specific pointers handy. I think libwww used to implement
>it... the part about
>	scheme1://auth1/path1 + scheme2:/path2 = scheme2://auth1/path2

libwww only ignored the scheme if both schemes were identical.

>This is the first time (I think) that it's been proposed to allow:
>
>	scheme1://auth1/path11/path12 + scheme2:../path2
>		= scheme2://auth1/path11/path2
>
>In any case, I doubt you're
>going to get a change to the relative URI parsing
>algorithm at this stage. It's just too widely deployed.

It also wouldn't make any sense to do that given that not all URI
use the //hostname syntax and therefore such a notion would cause
the relative URI parsing to be scheme-dependent.  That would suck.

....Roy

Received on Tuesday, 20 June 2000 17:00:54 UTC