Hi James,
James Gray wrote:
On Sat, 19 Feb 2005 12:45 am, Ralf Hildebrandt wrote:
When I surf to http://www.abstractserver.de/da2005/avi/e/Abs_revi.htm and enter any number/character and click "Submit my query", I get an error page ("Invalid Response" The HTTP Response message received from the contacted server could not be understood or was otherwise malformed. Please contact the site operator. Your cache administrator may be able to provide you with more details about the exact nature of the problem if needed. ) and in my cache.log:
I've been following this thread with interest as I experienced similar problems with a website after "apt-get upgrade" last week to 2.5S7 in Debian (Woody + backports.org). If it makes you feel any better, a local site is (was) pulling the same stunt: http://www.ht.com.au/
I called their IT people yesterday and gave them the details to which they were rather receptive. Indeed, they had $CLUE. They called me back in the afternoon to advise they had installed a patch at their end and wanted me to test it. Working again - balance is restored and the good guys (us) win :)
Oops, still not looking real great:
[root@tornado tmp]# wget -S www.ht.com.au --12:12:57-- http://www.ht.com.au/ => `index.html' Resolving www.ht.com.au... 203.28.63.40 Connecting to www.ht.com.au[203.28.63.40]:80... connected. HTTP request sent, awaiting response... 1 HTTP/1.1 302 Object moved 2 Server: Microsoft-IIS/5.0 3 Date: Mon, 21 Feb 2005 23:13:17 GMT 4 X-Powered-By: ASP.NET 5 Connection: keep-alive 6 Location: /scripts/xworks.exe?THEME:G 7 Connection: Keep-Alive 8 Content-Length: 121 9 Content-Type: text/html 10 Set-Cookie: ASPSESSIONIDAAARCBTQ=KNNGGGHDJNNBLGNCBPPENAFN; path=/ 11 Cache-control: private Location: /scripts/xworks.exe?THEME:G [following] --12:12:58-- http://www.ht.com.au/scripts/xworks.exe?THEME:G => `xworks.exe?THEME:G.1' Connecting to www.ht.com.au[203.28.63.40]:80... connected. HTTP request sent, awaiting response... 1 HTTP/1.1 200 OK 2 Server: Microsoft-IIS/5.0 3 Date: Mon, 21 Feb 2005 23:13:17 GMT 4 X-Powered-By: ASP.NET 5 HTTP/1.0 200 OK 6 Content-type: text/html 7 Set-Cookie: THEME=G; path=/ 8 P3P: CP="IDC NID CURa TAIa PHY ONL HISa DELa IND STA"
[ <=> ] 353 --.--K/s
12:12:58 (29.86 KB/s) - `xworks.exe?THEME:G.1' saved [353]
Want to let them know that they are still sending too many keep-alive headers?
More generally, how on earth does software manage to screw up something simple like an HTTP header so much? Is it usually an application that just appends duplicate headers to what was an existing and legitimate header from a web server? Or are there known-to-be broken versions of applications out there?
reuben
