tree 0972b19068c79955a616d96d175fcd7694dc1bef
parent 12b32f212f4c7457eeae37edb06dd0a06995fce1
author Willy Tarreau <w@1wt.eu> 1513953311 +0100
committer Willy Tarreau <w@1wt.eu> 1513954155 +0100
encoding latin1

BUG/MINOR: http: properly detect max-age=0 and s-maxage=0 in responses

In 1.3.8, commit a15645d ("[MAJOR] completed the HTTP response processing.")
improved the response parser by taking care of the cache-control header
field. The parser is wrong because it is split in two parts, one checking
for elements containing an equal sign and the other one for those without.
The "max-age=0" and "s-maxage=0" tests were located at the wrong place and
thus have never matched. In practice the side effect was very minimal given
that this code used to be enabled only when checking if a cookie had the
risk of being cached or not. Recently in 1.8 it was also used to decide if
the response could be cached but in practice the cache takes care of these
values by itself so there is very limited impact.

This fix can be backported to all stable versions.