tree c9b759f6de16afec8efef27b6f6c689f89adb218
parent 2b5c5cbef6bfac8effa6afa7e3a49d215d3cc60a
author Remi Tricot-Le Breton <rlebreton@haproxy.com> 1608743626 +0100
committer Willy Tarreau <w@1wt.eu> 1608826680 +0100
encoding latin1

BUG/MINOR: cache: Manage multiple headers in accept-encoding normalization

The accept-encoding part of the secondary key (vary) was only built out
of the first occurrence of the header. So if a client had two
accept-encoding headers, gzip and br for instance, the key would have
been built out of the gzip string. So another client that only managed
gzip would have been sent the cached resource, even if it was a br resource.
The http_find_header function is now called directly by the normalizers
so that they can manage multiple headers if needed.
A request that has more than 16 encodings will be considered as an
illegitimate request and its response will not be stored.

This fixes GitHub issue #987.

It does not need any backport.