- From: Lisa Dusseault <lisa@osafoundation.org>
- Date: Wed, 12 May 2004 10:04:39 -0700
- To: "Stanley Guan" <stanley.guan@oracle.com>
- Cc: <w3c-dist-auth@w3.org>
I'm a little confused. Which document are you looking at, RFC2518 or
RFC2518 bis (and if so, which draft?)
RFC2518 doesn't support commas in the If header, which is unfortunate
because it doesn't allow the sender to split the header up into several
headers. Normal HTTP composition rules allow the sender to do that, and
the entire header is reconstructed by adding in commas.
Lisa
On May 4, 2004, at 10:30 AM, Stanley Guan wrote:
> As shown in the Example, list items are separated by ",".
> Is this implied by the notation "1*"? Why "," is not
> explicitly specified in the derivation rules? Can we use
> space character instead of "," as separator?
>
> Thx,
>
> -Stanley
>
>
> 9.5 If Header
>
> If = "If" ":" ( 1*No-tag-list | 1*Tagged-list)
> No-tag-list = List
> Tagged-list = Resource 1*List
> Resource = Coded-URL
> List = "(" 1*(["Not"](State-token | "[" entity-tag "]")) ")"
> State-token = Coded-URL
> Coded-URL = "<" absoluteURI ">"
>
> 9.5.4 Example - Tagged List If header
>
> COPY /resource1 HTTP/1.1
> Host: www.example.com
> Destination: http://www.example.com/resource2
> If: <http://www.example.com/resource1> (<locktoken:a-write-lock-
> token> [W/"A weak ETag"]), (["strong ETag"]),
> <http://www.bar.bar/random>(["another strong ETag"])
>
Received on Wednesday, 12 May 2004 13:04:59 UTC