- From: Zhong Yu <zhong.j.yu@gmail.com>
- Date: Mon, 6 Feb 2012 20:21:11 -0600
- To: Mark Nottingham <mnot@mnot.net>
- Cc: Julian Reschke <julian.reschke@gmx.de>, Amos Jeffries <squid3@treenet.co.nz>, ietf-http-wg@w3.org
Since OWS and BWS include obs-fold, that would allow generation of 1 GET / HTTP/1.1 2 Host: 3 4 www.example.com 5 6 Accept: * 7 where line 3 and 5 contain spaces. The intention seems to be to forbid line folding anywhere in the message head. CR/LF are already forbidden in request/response line(specifically mentioned in RFC 2616). What's left is 'header-field'. On Mon, Feb 6, 2012 at 7:18 PM, Mark Nottingham <mnot@mnot.net> wrote: > I think "field-value" would work... > > > On 01/02/2012, at 8:00 AM, Julian Reschke wrote: > >> On 2012-01-30 01:14, Zhong Yu wrote: >>> p1 section 3.2.1. >>> >>> HTTP senders MUST NOT produce messages that include >>> line folding (i.e., that contain any #field-content# that matches the >>> obs-fold rule) >>> >>> shouldn't that be >>> >>> HTTP senders MUST NOT produce messages that include >>> line folding (i.e., that contain any #header-field# that matches the >>> obs-fold rule) >>> >>> instead? >>> >>> OWS = *( SP / HTAB / obs-fold ) >>> BWS = OWS >>> >>> header-field = field-name ":" OWS field-value BWS >>> field-name = token >>> field-value = *( field-content / obs-fold ) >>> field-content = *( HTAB / SP / VCHAR / obs-text ) >> >> Minimally, this is phrased confusingly. Not being sure what the best fix is, I opened a ticket: <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/335> >> >> Best regards, Julian >> >> > > -- > Mark Nottingham http://www.mnot.net/ > > >
Received on Tuesday, 7 February 2012 02:25:24 UTC