vary

How to ensure my CDN caches CORS requests by origin?

由 我怕爱的太早我们不能终老 提交于 2019-12-24 09:04:04
问题 I currently use Akamai as a CDN for my app, which is served over multiple subdomains. I recently realized that Akamai is caching CORS requests the same, regardless of the origin from which they were requested. This of course causes clients that make requests with a different Origin than the cached response to fail (since they have a different response header for Access-Control-Allow-Origin than they should) Many suggest supplying the Vary: Origin request header to avoid this issue, but

what does this configuration in apache mean? [closed]

由 落爺英雄遲暮 提交于 2019-12-01 04:16:34
Header append Vary User-Agent env=!dont-vary Can anyone give a detailed explanation for this? This uses Apache mod_headers to append the value "User-Agent" to the Vary HTTP header, but only if the dont-vary environment is not set. But what is the Vary header? See RFC2616 which says The Vary field value indicates the set of request-header fields that fully determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request without revalidation If you deliver different HTML markup depending on the User-Agent header, you might use a Vary

what does this configuration in apache mean? [closed]

由 有些话、适合烂在心里 提交于 2019-12-01 01:14:07
问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 6 years ago . Header append Vary User-Agent env=!dont-vary Can anyone give a detailed explanation for this? 回答1: This uses Apache mod_headers to append the value "User-Agent" to the Vary HTTP header, but only if the dont-vary environment is not set. But what is the Vary header? See RFC2616 which says The Vary field value
订阅 vary