Content-Base: http:///s//a/b/cin order to test a notion that Tim Berners-Lee mentioned regarding the ability of URIs to have a triple-slash (or even more slashes) to indicate higher levels of hierarchy than those already used by URLs. This is the same as Part 4, except that the scheme "fred" is replaced with "http" for clients that stupidly change their parsing behavior based on the scheme name.
Draft 09 assumes that a triple-slash means an empty site component, as does Netscape Navigator if the scheme is known. Oddly, Lynx seems to straddle both sides.
RESULTS from g:h = g:h [R,Tim,2,3] http:///s//a/b/g:h [1] g = http:///s//a/b/g [R,Tim,1,2,3] ./g = http:///s//a/b/g [R,Tim,1,2,3] g/ = http:///s//a/b/g/ [R,Tim,1,2,3] /g = http:///g [R,1,2,3] http:///s//a/g [Tim] //g = http://g [R,1,2,3] http:///s//g [Tim] //g/x = http://g/x [R,1,2,3] http:///s//g/x [Tim] ///g = http:///g [R,Tim,1,2,3] ./ = http:///s//a/b/ [R,Tim,1,2,3] ../ = http:///s//a/ [R,Tim,1,2,3] ../g = http:///s//a/g [R,Tim,1,2,3] ../../ = http:///s// [R,1] http:///s//a/../ [Tim,2] http:///s//a/ [3] ../../g = http:///s//g [R,1] http:///s//a/../g [Tim,2] http:///s//a/g [3] ../../../g = http:///s/g [R,1] http:///s//a/../../g [Tim,2] http:///s//a/g [3] ../../../../g = http:///g [R,1] http:///s//a/../../../g [Tim,2] http:///s//a/g [3]