HP Cloud CDN & DNS : Far Set Expires to Leverage Caching

50 Years Expires May Not Work. Far Set Expires to Leverage Caching in HP Cloud CDN & DNS By Setting Container TTL to 5 Years & Same For DNS. Programmatically we can change the Expire Headers in OpenStack Object Storage or Swift on HP Cloud. Thats great, but actually setting the container TTL to a higher values do the same work for only setting the expire headers.

HP Cloud CDN & DNS : What Are the Pitfalls in Far Set Expires to Leverage Caching

50 years or 1577836800 seconds possibly can not write the data on Akamai’s container. Using 5 years value (157783680 seconds) works fine. Second unfortunate thing is that – the HTTPS links will not get the Expire Header changed. For example, this is a working example :

But for the corresponding HTTPS URL :

Cache-Control: public, max-age=42206 – too low and has no fix discovered by us.

HP Cloud CDN & DNS : How To Far Set Expires to Leverage Caching

Very easy. Login to HP Cloud Horizon Web GUI. If you have any published container as CDN, click the down arrow button beside the name of the container :

Click to Edit the TTL and you will get a pop up window. Editing the TTL to 5 years (i.e. 157783680 seconds) will do the work for all the non-HTTPS URLs against the objects in the container. However, the HTTPS URLs will lag behind!

We guess, the TTL of A record and AAAA record should maximum raised to 157783680 seconds. 50 years probably triggers some errors in Akamai’s end – 50 years is officially supported max time by Akamai. You’ll get TTL of a domain in this way :

You have to Edit from DNS’s Web GUI. Geographical Distribution of HP Cloud – Akamai ‘s DNS system & Authority Servers are very complex and not possible for us to modify the value to huge extent. This command will give you better idea :

Change thecustomizewindows.com with your domain name.