Apache sending Simple-Response header
Posted: Tue Oct 18, 2005 1:24 pm
This is a fun one!
I'm having a problem with Apache sending Gecko* based browsers funky headers every once in a while. At least 1 out of 6 https:// connections result in the server sending back an HTTP/1.0 200 Simple-Response header. This should never be happening, as the other 5 out of 6 times, it sends either an HTTP/1.0 200 OK header or an HTTP/1.1 200 OK header.
The result: for that 1/6 connections, I get a zero displayed, then all the headers dumped as text, then the web page dumped as text, and not rendered as HTML. Sometimes, though, the HTML does render - I haven't been able to pin down the conditions for that.
* This only applies to current, Gecko based browsers. I've tested FF 1.07 on Mac and Windows, FF 1.06 on Windows, and Netscape 7.2. Safari 2.0 doesn't seem to be affected, nor is FF 1.5 Beta 2, or FF 0.92
I've got a HTTP analyzer on my computer and I've noticed the request headers Firefox sends are absolutely no different between a successful response and a buggered response.
Here are the headers being sent from Firefox that resulted in an HTTP/1.0 200 Simple-Response header
And here are the headers being sent from IE that resulted in a perfectly fine page load
Now for some more weird stuff. While I'm currently only concerning myself with one server, we've got another one here that is exhibiting similar behaviour in Firefox. Further, the current server I'm trying to fix serves multiple subdomains. I can access a virtually hosted subdomain just fine all day long without any problems. However, when I access the actual subdomain, I get this problem consistently.
Has anyone ever had this problem? Is this a bug in Apache or Firefox, or is our installation of Apache starting to crater? If anyone needs any more information, please don't hesitate to ask.
Thanks a bunch!
I'm having a problem with Apache sending Gecko* based browsers funky headers every once in a while. At least 1 out of 6 https:// connections result in the server sending back an HTTP/1.0 200 Simple-Response header. This should never be happening, as the other 5 out of 6 times, it sends either an HTTP/1.0 200 OK header or an HTTP/1.1 200 OK header.
The result: for that 1/6 connections, I get a zero displayed, then all the headers dumped as text, then the web page dumped as text, and not rendered as HTML. Sometimes, though, the HTML does render - I haven't been able to pin down the conditions for that.
* This only applies to current, Gecko based browsers. I've tested FF 1.07 on Mac and Windows, FF 1.06 on Windows, and Netscape 7.2. Safari 2.0 doesn't seem to be affected, nor is FF 1.5 Beta 2, or FF 0.92
I've got a HTTP analyzer on my computer and I've noticed the request headers Firefox sends are absolutely no different between a successful response and a buggered response.
Here are the headers being sent from Firefox that resulted in an HTTP/1.0 200 Simple-Response header
Code: Select all
Request Headers Value
(Request-Line) GET /test.html HTTP/1.1
Host my.domain.ca
User-Agent Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Accept text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
Accept-Language en-us,en;q=0.5
Accept-Encoding gzip,deflate
Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive 300
Connection keep-alive
Cookie PHPSESSID=e81eb8eab3254f6fbb679bae8d30a817
Pragma no-cache
Cache-Control no-cacheCode: Select all
Request Headers Value
(Request-Line) GET /test.html HTTP/1.1
Accept */*
Accept-Language en-us
Accept-Encoding gzip, deflate
User-Agent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Host my.domain.ca
Connection Keep-Alive
Cache-Control no-cache
NovINet v1.0Has anyone ever had this problem? Is this a bug in Apache or Firefox, or is our installation of Apache starting to crater? If anyone needs any more information, please don't hesitate to ask.
Thanks a bunch!