tree b99438a641529c10ec02a686cf83deaf376725e7
parent bcced09b91c510685b8bd6cb264a5d49c6fd472d
author Remi Tricot-Le Breton <rlebreton@haproxy.com> 1603356004 +0200
committer William Lallemand <wlallemand@haproxy.org> 1603375820 +0200

MEDIUM: cache: Store the ETag information in the cache_entry

When sent by a server for a given resource, the ETag header is
stored in the coresponding cache entry (as any other header). So in
order to perform future ETag comparisons (for subsequent conditional
HTTP requests), we keep the length of the ETag and its offset
relative to the start of the cache_entry.
If no ETag header exists, the length and offset are zero.