On Wednesday, September 11, 2002, at 06:04 PM, Graham Leggett wrote: > Kris Verbeeck wrote: > >>>> The response: >>>> >>>> HTTP/1.0 200 >>>> Date: Tue, 10 Sep 2002 09:45:39 GMT >>>> Server: web server >>>> Connection: close >>>> etag: "b9829-2269-3cd12aa1" >>> >>> Another bug - why is an HTTP/1.1 response prefixed with "HTTP/1.0"...? >> Nope, there is a force-response-1.0 in httpd.conf for this request. So >> normal behaviour. > > Both Etag and Connection: close are HTTP/1.1 headers, simply changing the > version string on a forced-response-1.0 is wrong as I understand it. > > Can someone clarify what should happen in this case?
No, they are HTTP/1.x headers (there is no such thing as a 1.1 header, only features that cannot be sent in response to a 1.0 request). Both connection and etag should be sent regardless of protocol version. ....Roy
