]> git.ipfire.org Git - thirdparty/squid.git/commit
Do not duplicate received Surrogate-Capability in sent requests (#2087)
authorEduard Bagdasaryan <eduard.bagdasaryan@measurement-factory.com>
Tue, 17 Jun 2025 21:00:51 +0000 (21:00 +0000)
committerSquid Anubis <squid-anubis@squid-cache.org>
Wed, 18 Jun 2025 14:11:15 +0000 (14:11 +0000)
commitc6bdd8969fad2ad912b2a09fe7ba031d87a31d0d
tree3676f48591ace0ed25ac0681f2977aeaabecf7d7
parent1a75283ffdd2e1d2aac80dfebe97fd1bc6b9bf39
Do not duplicate received Surrogate-Capability in sent requests (#2087)

When computing Surrogate-Capability header while forwarding an
accelerated request, Squid duplicated old (i.e. received) header entries
(if any). For example, this outgoing request shows an extra hop1 entry:

    GET / HTTP/1.1
    ...
    Surrogate-Capability: hop1="Surrogate/1.0"
    Surrogate-Capability: hop1="Surrogate/1.0", hop2="Surrogate/1.0"
src/http.cc