At 16:30 23-11-97 -0700, Marc Slemko wrote:
>> Ehh... isn't it actually the underlying filesystem that treats them as
equal?
>No.
>The filesystem treating them as equal never gets to enter into the picture
>because no2slash() already collapses them.
Aha!
Still, the only valid reason I can see for "//" in a URL is as part of a
protocol specification: so "//" by itself should be collapsed, but "://"
not... Wouldn't that fix the problem?
Elizabeth Mattijsen
xxLINK Internet Services