[英]Why is Akamai cache-control max-age decreasing value?
I am using Akamai and the cache-control
headers max-age
value is decreasing on each subsequent request when using honor origin cache control + expires .我正在使用 Akamai 并且当使用Honor origin cache control + expires时,
cache-control
标头max-age
值在每个后续请求中都在减少。 On other CDNs I don't experience the same behaviour.在其他 CDN 上,我没有遇到相同的行为。
On the app I have Cache-Control: max-age=2592000, public
and the max-age value in the response headers seems to be calculated as the time Akamai fetched the asset from the server minus the max-age specified in the app.在应用程序上,我有
Cache-Control: max-age=2592000, public
和响应标头中的 max-age 值似乎计算为 Akamai 从服务器获取资产的时间减去应用程序中指定的 max-age。
Why is this happening?为什么会这样? How can I have Akamai respond with
max-age=2592000, public
?我如何让 Akamai 响应
max-age=2592000, public
?
You can easily configure this via "Downstream cacheability" behaviour: » "Pass cacheability headers from origin" » This tunnels the Cache-Control and/or Expires header settings from the origin to the downstream.
您可以通过“下游可缓存性”行为轻松配置:»“从源传递可缓存性标头”» 这将缓存控制和/或过期标头设置从源头传输到下游。
Alternatively, for resources with TTL defined at the Edge you can set this to "Full edge TTL (max-age)".
或者,对于在 Edge 定义了 TTL 的资源,您可以将其设置为“Full edge TTL (max-age)”。
Thanks to @TimVereeke.感谢@TimVereeke。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.