Re: $url->path

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Gisle Aas: "Re: $url->path"
• Previous message: Gisle Aas: "$url->path"
• Maybe in reply to: Gisle Aas: "$url->path"
• Next in thread: Gisle Aas: "Re: $url->path"

> Can anybody explain the rationale behind stating that "/" is *NOT*
> part of the path?

It is a long and painfull story, but the gist of it is that

     http://site
and  http://site/

are equivalent because the "/" is a separator and not part of the path.
Naturally, this leads to all sorts of confusion because it is part of
the path during an HTTP request.

This is what happens when standards are written without regard for
how the standard is used -- what it should have said is that the
slash is part of the path and that the path defaults to "/" when
nothing is present.  Unfortunately, the URI WG did not have a
sufficient number of HTTP implementors in attendance.


 ...Roy T. Fielding
    Department of Information & Computer Science    (fielding@ics.uci.edu)
    University of California, Irvine, CA 92717-3425    fax:+1(714)824-4056
    http://www.ics.uci.edu/~fielding/

• Next message: Gisle Aas: "Re: $url->path"
• Previous message: Gisle Aas: "$url->path"
• Maybe in reply to: Gisle Aas: "$url->path"
• Next in thread: Gisle Aas: "Re: $url->path"