mlibbey commented on issue #7671:
URL: https://github.com/apache/trafficserver/issues/7671#issuecomment-826145469


   `cache-control: private, must-revalidate, max-age=0`
   - `private` means that caches that are solely dedicated to individuals (like 
your browser) can cache. This is the biggie -- need to change this to public
   - `must-revalidate, max-age=0` ... these mean that the cache could store 
them, but, need to talk to origin server each and every time to make sure the 
object can be released. I believe that `no-cache` is the more direct way of 
indicating this combination. Either way, its a terrible combination for Traffic 
Server, as it will make any read-while-write (eg request collapsing) requests 
go in serial.
   - There is also an `expires: Sat, 24 Apr 2021 15:34:15 GMT` -- which matches 
the date, which is also saying the object immediately is stale.
   - The origin server also says to vary on encoding (makes sense -- compressed 
v non-compressed), cookie and Authorization (which will very likely be unique 
to each user ... perhaps why they put in private). There are settings for the 
number of variants, but, with a variant per user, it seems like it'd be 
difficult to choose a reasonably number. 
   
   Ideally, the origin server folks would rethink their choices above. 
Alternatively, you can use the header_rewrite plugin to override their 
decisions -- remove/replace the headers as you deem necessary.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to