Skip to content

Instantly share code, notes, and snippets.

@normanzb

normanzb/Akamai_Cache_CDN.md

Created November 21, 2019 22:59
Show Gist options
  • Save normanzb/bd31cc6691508f68a306745c7bc7c02c to your computer and use it in GitHub Desktop.
Save normanzb/bd31cc6691508f68a306745c7bc7c02c to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Akamai_Cache_CDN.md

https://developer.akamai.com/blog/2017/03/28/what-you-need-know-about-caching-part-1 https://developer.akamai.com/akamai-101-basics-purging

Configuring Akamai with the Luna Control Center

When configuring caching settings on Akamai’s Luna Control Center, you would utilize Property Manager to set up various rules. The Caching behavior gives you five options in the drop down list:

  • honor origin cache control + expires - indicates that Akamai servers should respect both of the Cache-Control & Expires headers received from your servers.
  • honor origin cache control - indicates that Akamai servers should only respect the Cache-Control header received from your backend servers.
  • honor origin expires - tells the Akamai servers to only respect the Expires header received from your backend servers. Note: when selecting any of these three options, you need to define a default Max-Age which will be used in the case where your servers do NOT return any of the specified headers.
  • cache - lets you define the Time-To-Live (TTL) of all assets served through Akamai, regardless of what your servers indicate in the Cache-Control or Expires headers. We recommend this for all your static assets. no store - prevents the Akamai cache from storing a copy of the file, and always requests a new copy from your backend servers. We recommend this for your dynamic HTML or API calls.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment