Re: [squid-users] Re: Problem with unparseable HTTP header field

* M A Young <m.a.young@durham.ac.uk>:

> before the contents of the web page. If you fetch that page by hand (eg.
> with wget -S) you can see the HTTP headers
> 1 HTTP/1.0 200 OK
> 2 Server: Microsoft-IIS/3.0
> 3 Date: Fri, 18 Feb 2005 19:54:50 GMT
> 4 HTTP/1.1 200 OK
> 5 content-type: text/html
> 6 content-length: 2617
> 7 Connection: Keep-Alive
> which is difficult to make sense of if you actually try to understand it;
> is the answer HTTP/1.1 or HTTP/1.0?

I was able to reproduce that. So the server sends TWO "HTTP" headers?
First the HTTP/1.0 header in line 1 and then HTTP/1.1 on line 4?

Am I getting this right?
Who codes this shit?

-- 
Ralf Hildebrandt (i.A. des IT-Zentrum)          Ralf.Hildebrandt@charite.de
Charite - Universitätsmedizin Berlin            Tel.  +49 (0)30-450 570-155
Gemeinsame Einrichtung von FU- und HU-Berlin    Fax.  +49 (0)30-450 570-962
IT-Zentrum Standort CBF                 send no mail to spamtrap@charite.de