RE: Collections and Request-URIs

> From: w3c-dist-auth-request@w3.org
> [mailto:w3c-dist-auth-request@w3.org]On Behalf Of Jim Luther
> Sent: Tuesday, June 18, 2002 1:46 AM
> To: w3c-dist-auth@w3c.org
> Subject: Collections and Request-URIs
>
>
>
> RFC 2518, section 5.2 says:
>
> "There is a standing convention that when a collection is referred to by
> its name without a trailing slash, the trailing slash is automatically
> appended.  Due to this, a resource may accept a URI without a
> trailing "/" to point to a collection. In this case it SHOULD return a
> content-location header in the response pointing to the URI ending with
> the "/". For example, if a client invokes a method on
> http://foo.bar/blah (no trailing slash), the resource
> http://foo.bar/blah/ (trailing slash) may respond as if the operation
> were invoked on it, and should return a content-location header with
> http://foo.bar/blah/ in it.  In general clients SHOULD use the "/" form
> of collection names."
>
> It looks to me like the "standing convention" doesn't match the BNF. RFC
> 2616, section 5.1.2 gives this rule for the Request-URI in the
> Request-Line:
>
> 	Request-URI 	= "*" | absoluteURI | abs_path | authority
>
> and RFC 2396, section 3 gives these rules for abs_path and path_segments:
>
> 	abs_path      = "/"  path_segments
> 	path_segments = segment *( "/" segment )
>
> So by my reading, abs_path should not have a trailing slash. Did I miss
> something? If not, I think the WebDAV spec should say that servers MUST
> handle Request-URIs to collections without the trail slash.

However:

segment       = *pchar *( ";" param )
param         = *pchar

pchar         = unreserved | escaped |
                ":" | "@" | "&" | "=" | "+" | "$" | ","

([1]) and

"The second convention is a BNF-like grammar, used to define the formal URI
syntax. The grammar is that of [RFC822], except that "|" is used to
designate alternatives. Briefly, rules are separated from definitions by an
equal "=", indentation is used to continue a rule definition over more than
one line, literals are quoted with "", parentheses "(" and ")" are used to
group elements, optional elements are enclosed in "[" and "]" brackets, and
elements may be preceded with <n>* to designate n or more repetitions of the
following element; n defaults to 0."

([2]). So it seems that "segment" may be empty.

Julian



[1] <http://greenbytes.de/tech/webdav/rfc2396.html#rfc.section.3.3>
[2] <http://greenbytes.de/tech/webdav/rfc2396.html#rfc.section.1.6>

Received on Tuesday, 18 June 2002 02:17:31 UTC