Random things I'm likely to forget
!!! downstream-ttl Default setup ignores cache-control max-age and will return the time left before the object is set to expire from its cache. So if you have an object cached for a year and users are hitting it on day 364 they will only have it cached for a day before they need to refetch it.
There are 2 ways to change this if it is not your desired behavior.
- Send Edge-Control an edge control header with the same expire time as your max-age. ex. Edge-Control "downstream-ttl=86400"
- Reconfigure your Akamai instance to honor the max-age.
!!! serving 304 instead of a file In some configurations if you change the cache time on a source object but do not change the object, Akamai will return 304s instead of the object. This is really bad if the requester doesn't actually have the object. The fix is to touch the files so akamai will reload them. Apparently this is changing in future releases/configurations.
!! Making HTTP requests via telnet
This Deserves its own page