For all responses using private Cache-Control headers respond with Cache-control = private, no-cache
Motivation and Context
Our custom entry responses should not have a max_age as these can be updated at any time. By removing a max_age as the default for private caching we can achieve this result. This still allows for local caching, but requires the client to verify that the content has not been updated.
Description
For all responses using private Cache-Control headers respond with Cache-control = private, no-cache
Motivation and Context
Our custom entry responses should not have a max_age as these can be updated at any time. By removing a max_age as the default for private caching we can achieve this result. This still allows for local caching, but requires the client to verify that the content has not been updated.
How Has This Been Tested?
Tests have been updated.
Checklist: