Contents
Do Akamai cache headers?
By default, Akamai calculates the downstream caching lifetime based on your API-level caching instructions or your origin caching headers. If your API-level caching behavior is set to No store or Bypass cache, edge servers attempt to prohibit downstream caching by sending so-called cache-busting headers to clients.
What is Akamai caching?
At Akamai, caching refers to objects retrieved from your origin server and stored at any number of edge servers. Edge servers can quickly deliver the cached objects to your API consumers. Caching decreases the load on your origin server and reduces latency in serving objects to the end client.
By default Akamai caches cookie headers and passes them back to clients along with each response. If cookie information is updated on the request Akamai does not pass the updated cookie back to the client because it sends the cached content instead.
How do I find my Akamai headers?
Click on any row, then select Headers. It will show HTTP Request and Response headers for that specic object. If you see Pragma header is the Request Headers then this means the browser setup is correct.
What is the max age for caching in Akamai?
If you make a request against the server, it reveals that response caching is indeed enabled by the presence of a new header: cache-control. This header’s max-age value is set at 300 seconds (the 5 minutes we specified in the app):
How to set cache control in Akamai browser?
Akamai has a header called “Edge-control” of the same format as Cache-Control. You can specify the Edge-control with a positive max-age and then set Cache-Control to “no-cache, no-store”. This should get what you want.
How are HTTP headers used in Akamai Edge?
Akamai does provide a means to set different caching behaviour within the Akamai servers vs the usual Cache-Control: and Expires: headers. There are custom headers you can pass from your origin servers that the Akamai edge servers understand, obey and strip when they pass the content on to the browser.
Which is cache overrides max-age or Expires header?
Overrides max-age or the Expires header, but only for shared caches (e.g., proxies). Ignored by private caches. Indicates the client will accept a stale response. An optional value in seconds indicates the upper limit of staleness the client will accept.