]> git.ipfire.org Git - thirdparty/squid.git/commit
HTTP/1.1 compliance: Stop using Proxy-Connection header
authorAmos Jeffries <amosjeffries@squid-cache.org>
Wed, 18 Aug 2010 01:45:20 +0000 (19:45 -0600)
committerAmos Jeffries <amosjeffries@squid-cache.org>
Wed, 18 Aug 2010 01:45:20 +0000 (19:45 -0600)
commita96ed08df9e05d1c5bee21f4b6c3f1881a720d79
treefe1bcaf4eb7cc54e103b625b5959813c383ef0e1
parent9ee404e0a2140d69a72db1cecf02bcecec4e3a51
HTTP/1.1 compliance: Stop using Proxy-Connection header

The Proxy-Connection header is not part of any HTTP standard. It was added
by Netscape to differentiate persistent connections to intermediary proxies
but that duty has been formally superceded by the Connection: header.

This compliance update makes Squid stop sending Proxy-Connection on outbound
requests. Starts consistently using Connection: header instead.

The Proxy-Connection header is also ignored on HTTP-strict builds.
For compatibility we must do a small violation and drop it as a hop-by-hop
header despite strict-mode technically being required to pass it through.

For origin server connections the non-strict builds will retain the
status-quo: interpret it, but treat it as an HTTP/0.9 thing to be
upgraded to HTTP/1.1 Connection: header.

squidclient is also fixed not to send it.
src/HttpHeaderTools.cc
src/cf.data.pre
src/client_side_reply.cc
src/http.cc
tools/squidclient.cc