- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Wed, 21 Nov 2007 15:40:40 +0100
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
* Julian Reschke wrote: >> It's not clear to me that this needs to be allowed, and if so, it's >> unclear to me that this is the only case that needs to be allowed. > >It's unfortunate, but I think it would be a service to readers of the >spec to make them aware of that exception. I would not mind a note and certainly expect the State Management part to point this issue out, but allowing this practise is a different issue (that should be discussed in some other thread anyway). >> I disagree with this, for example, Apache will reject requests with >> multiple Content-Length headers with Request Entity Too Large, not > >I would consider that a bug; why would you say that the request entity >is too large if you don't know how large it is? Because that's what you get if the header is malformed in some other way and because it requires less logic in the server's code. This may not be ideal, but I can see no reason to outlaw this either. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Wednesday, 21 November 2007 14:41:01 UTC