- From: Anne van Kesteren <annevk@opera.com>
- Date: Fri, 02 Oct 2009 14:47:15 +0200
- To: "Julian Reschke" <julian.reschke@gmx.de>
- Cc: "Adam Barth" <abarth@cs.stanford.edu>, www-archive@w3.org
On Fri, 02 Oct 2009 14:42:29 +0200, Julian Reschke <julian.reschke@gmx.de> wrote: > Anne van Kesteren wrote: >> So I just read some things again and it seems CORS is already using >> comma-separated lists for some header formats. My thinking now is that >> we should just do the same for the Origin header. I think that would >> make it (per modified (future) ABNF rules from httpbis): >> origin = "Origin" ":" origin-value >> origin-value = "null" / #serialized-origin >> Apparently the OWS issue will be solved by future drafts of httpbis. > > The #list rule should be used as a top-level construct, see > > "Multiple message-header fields with the same field-name MAY be present > in a message if and only if the entire field-value for that header field > is defined as a comma-separated list [i.e., #(values)]." -- > <http://greenbytes.de/tech/webdav/draft-ietf-httpbis-p1-messaging-07.html#rfc.section.4.2> > > So you'd need to make it: > > origin = "Origin" ":" origin-value > origin-value = #foobar > foobar = "null" / serialized-origin > > Of course that means "null" could appear multiple times; if that is a > problem than that header format may not be the right choice. I see. I suppose that as long as we impose restrictions on what clients are supposed to transmit this should not matter. > PS: note that "null" matches case-insensitively, is that intended? Case-sensitive would be better I guess. -- Anne van Kesteren http://annevankesteren.nl/
Received on Friday, 2 October 2009 12:47:56 UTC