]> git.ipfire.org Git - thirdparty/squid.git/commit - src/client_side_reply.cc
HTTP/1.1 compliance: Stop using Proxy-Connection header
authorAmos Jeffries <amosjeffries@squid-cache.org>
Fri, 13 Aug 2010 07:53:08 +0000 (01:53 -0600)
committerAmos Jeffries <amosjeffries@squid-cache.org>
Fri, 13 Aug 2010 07:53:08 +0000 (01:53 -0600)
commit95e785008cfde3ae4a0f830437dd768ce7afdb2e
treee5f8ac91c7166be9902e98e027053826b1fdef48
parentb283ea3fba03e8ceb3c886dc2fc03e474b7c30f9
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 strct-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:.

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