Seeking wisdom on URI path parameters.

[JanC]

Steven Taschuk <staschuk at telusplanet.net> schreef:

>     .;param=value/foo.html
[...]
> The RFC is sadly a bit vague on this point.  (The
> example algorithm makes no mention of parameters, and none of the
> examples in the appendix address this point.)

In 3.3.: "Each path segment may include a sequence of parameters, indicated 
by the semicolon ';' character."
--> note the use of "include".

In 5. it says: "Within a relative-path reference, the complete path segments 
'.' and '..' have special meanings: 'the current hierarchy level' and 'the 
level above this hierarchy level', respectively."
--> _complete_ segment must be '.' or '..'

So I would say:
http://localhost/dir;im_ignoring=this/subdir;and=this/.;param=value/foo.html
(whatever that may mean to the web server...)

And that's also exactly what the example algorithm does.

-- 
JanC

"Be strict when sending and tolerant when receiving."
RFC 1958 - Architectural Principles of the Internet - section 3.9