| 1:55 pm on Feb 14, 2012 (gmt 0)|
does the browser get a Cache-Control header from the CDN or an Expires header?
| 4:08 am on Mar 30, 2012 (gmt 0)|
The browser gets the Cache-Control header from the CDN.
In fact, the CDN forwards the cache headers set by my website.
Webserver => CDN => User
I want to set the header for CDN to cache content for 2 days, but the User should see the cache header set for 10 minutes. The reason is, I can manually purge the cache from the CDN whenever I update the content.
| 12:38 pm on Mar 30, 2012 (gmt 0)|
i would first check to see if there are custom/proprietary headers available for your CDN service that would get stripped before forwarding to browser requests.
| 1:55 pm on Mar 30, 2012 (gmt 0)|
My CDN forwards all the headers that were sent to it. Does something like public for visitors and must-revalidate for CDN work?
| 2:29 pm on Mar 30, 2012 (gmt 0)|
according to the Hypertext Transfer Protocol -- HTTP/1.1
|Cache directives MUST be passed through by a proxy or gateway application, regardless of their significance to that application, since the directives might be applicable to all recipients along the request/response chain. It is not possible to specify a cache- directive for a specific cache. |
this means you won't fix this without a CDN-specific cache control header.
| 3:35 am on Apr 1, 2012 (gmt 0)|
Seems, I have no solution to this problem. Thanks anyway.