On Thu, Mar 04, 2004 at 06:44:26PM -0000, Matthew J. Dovey wrote:
> " url-path
> The rest of the locator consists of data specific to the
> scheme, and is known as the "url-path". It supplies the
> details of how the specified resource can be accessed. Note
> that the "/" between the host (or port) and the url-path is
> NOT part of the url-path."
Gosh, things just don't stay the same do they. I have read other
specs (may be out of date now) that said almost the exact opposite.
They defined an abs_path rule that was "/" rooted. I think part of
the problem is there are many different RFCs that effectively redefine
the grammar for a URL. (Just do a google query for "abs_path" and you
cand find quite a few pretty quickly - eg:
mentions RFC 2616, RFC 2396, and RFC 1808).
I don't think it matters much though - I think you do whatever the
specific API says is necessary. If the API needs a "/" to be added,
then add it!