- From: Dan Winship <dan.winship@gmail.com>
- Date: Thu, 23 Sep 2010 09:36:25 -0400
- To: Bjoern Hoehrmann <derhoermi@gmx.net>
- CC: Julian Reschke <julian.reschke@gmx.de>, HTTP Working Group <ietf-http-wg@w3.org>
On 09/22/2010 04:22 PM, Bjoern Hoehrmann wrote: > 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). In my experience, egregiously broken HTTP responses tend to involve either (a) embedded HTTP servers (wifi hub config servers, etc), or (b) non-2xx responses. (Or both at once, as in https://bugzilla.gnome.org/show_bug.cgi?id=588658 and https://bugzilla.gnome.org/show_bug.cgi?id=588660.) -- Dan
Received on Thursday, 23 September 2010 13:36:57 UTC