3 ms·
Response #1: date:Wed, 07 Sep 2016 21:41:23 GMT expires:Wed, 07 Sep 2016 21:41:53 GMT Response #2: date:Wed, 07 Sep 2016 21:41:23 GMT exp
by matt4077 10y ago
Response #1:
date:Wed, 07 Sep 2016 21:41:23 GMT
expires:Wed, 07 Sep 2016 21:41:53 GMT
Response #2:
date:Wed, 07 Sep 2016 21:41:23 GMT
expires:Thu, 07 Sep 2017 21:41:23 GMT
> Although the two expires headers are almost identical, they can only be Huffman compressed, because they can't be matched in full.
It seems like it'd be be an easy win to round expiry times to the nearest minute/hour/day. At least for requests such as these where that value is one year in the future.
- niftich 10y agoThis. For HTTP 1.1 clients, Cache-Control already overrides anything set in Expires (a header dating to HTTP 1.0), so losing some precision on an approximate guess far into the future that's bound to be ignored by most clients should be a sensible trade-off.