- From: Mark Nottingham <mnot@mnot.net>
- Date: Mon, 27 Feb 2012 17:47:54 +1100
- To: HTTP Working Group <ietf-http-wg@w3.org>
- Cc: "Julian F. Reschke" <julian.reschke@gmx.de>, Roy Fielding <fielding@gbiv.com>
OK, I'm marking this one as WONTFIX. Editors, feel free to incorporate Roy's pithy "The ABNF defines what is valid to send, not what is robust to parse" in p1 1.1 (and elsewhere as appropriate). On 21/02/2012, at 4:46 PM, Roy T. Fielding wrote: > On Feb 20, 2012, at 8:31 PM, Mark Nottingham wrote: > >> OK, but currently we don't talk about multiple spaces (or other whitespace) in the top-line anywhere; what's the appropriate vehicle? > > There is no vehicle needed. As I said in the ticket, the only interoperable behavior > is to send a single SP. If some implementations choose to receive more than one space, > that's their choice -- it is still not interoperable to send more than one space. > The ABNF defines what is valid to send, not what is robust to parse. I'd rather change > Apache httpd's parser to forbid extra spaces than make the request-line less predictable. > > ....Roy > > -- Mark Nottingham http://www.mnot.net/
Received on Monday, 27 February 2012 06:48:23 UTC