- From: Mark Nottingham <mnot@mnot.net>
- Date: Sun, 12 Jul 2009 11:01:34 +1000
- To: Adam Barth <w3c@adambarth.com>
- Cc: Ian Hickson <ian@hixie.ch>, collinj@cs.stanford.edu, HTTP Working Group <ietf-http-wg@w3.org>
On 09/07/2009, at 3:58 PM, Adam Barth wrote: > >> * The header field-value is defined as containing LWS characters. >> There >> isn't a reference for that rule, and FYI that form is being >> deprecated by >> HTTPbis; it would probably be better to say one or more whitespace >> characters. Another option would be to make it a comma-separated >> list, to >> pull it in line with the definitions of other HTTP headers. > > My understanding is that using a comma-separated list would change the > semantics because of header coalescing. How so? I.e., does this: Sec-From: a.com b.com, c.com d.com place an semantic significance on the split between a/b and c/d? > Saying "whitespace" seems > less precise than LWS. Is whitespace defined precisely somewhere in > HTTPbis that I can reference? Best thing do to would be to reference WS in RFC5234. -- Mark Nottingham http://www.mnot.net/
Received on Sunday, 12 July 2009 01:02:48 UTC