You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the accept-encoding header is only added to the vary header when the response contains a content-encoding. This works but can cause intermediate caches to only return the non-encoded response when an initial request does not contain a compatible content-encoding, causing compatible clients to receive non-encoded content.
To fix this, accept-encoding should be added to the vary header to all payload containing responses with compressible content.
The text was updated successfully, but these errors were encountered:
Currently the
accept-encoding
header is only added to thevary
header when the response contains a content-encoding. This works but can cause intermediate caches to only return the non-encoded response when an initial request does not contain a compatiblecontent-encoding
, causing compatible clients to receive non-encoded content.To fix this,
accept-encoding
should be added to thevary
header to all payload containing responses with compressible content.The text was updated successfully, but these errors were encountered: