- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Wed, 22 Sep 2010 22:22:34 +0200
- To: Julian Reschke <julian.reschke@gmx.de>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
* Julian Reschke wrote: >Agreed, but it makes the spec more complex, and it's not sure whether >it's worth the special case (that's why statistical data would be useful). Earlier this week I had http://cutycapt.sf.net/ load a bunch of URLs (random selection of pages linked from the german Wikipedia, at most three per host) resulting in about 125,000 requests. There was not a single response with both Transfer-Encoding and Content-Length, or two or more Content-Length headers, or Content-Length headers with any- thing but digits and white space (especially no commas). Neither does this happen for the Alexa 1000. Obviously this does not include certain things like responses resulting from user interaction (say, posting to a forum). It's a lot harder these days to get webservers send out messages with broken framing, thanks to improvements to script interpreters, web servers, and the interfaces between them, than it was a few years ago. (The usual strange things are included, like headers that end up as a reason phrase in the status line of the response ala "HTTP/1.0 200 OKContent-Type: text/html; char..."; portugese appears to be the most popular language second to english in the reason phrase by the way, followed by german and serbian...) -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Wednesday, 22 September 2010 20:49:52 UTC