]> git.ipfire.org Git - thirdparty/squid.git/commit
HTTP/1.1: Update all stored headers on 304 revalidation.
authorEduard Bagdasaryan <eduard.bagdasaryan@measurement-factory.com>
Sat, 25 Jun 2016 14:35:41 +0000 (02:35 +1200)
committerAmos Jeffries <squid3@treenet.co.nz>
Sat, 25 Jun 2016 14:35:41 +0000 (02:35 +1200)
commit2d4f252d95dcf979601552f2c86fae980beff05f
treeb8ec2d8f714376fb9891d48d3f2f844f7e52ea53
parent4dc4090b6f49b4f85f9edb27c550f7341f1f966e
HTTP/1.1: Update all stored headers on 304 revalidation.

According to RFC 7234 section 4.3.4. when a proxy receives 304 (Not Modified)
response, it should update every header, except Warning headers (which need
special processing). Also RFC 7232 section 4.1. does not prohibit origin servers
from sending any headers in 304 responses. That means that Squid now should not
ignore headers, which earlier were considered as malicious/faulty.
src/HttpHeader.cc
src/HttpHeader.h
src/HttpReply.cc
src/adaptation/History.cc
src/client_side_request.cc
src/http/RegisteredHeadersHash.cci
src/http/RegisteredHeadersHash.gperf
src/main.cc
src/tests/testRock.cc
src/tests/testUfs.cc