Cache Control

Cache Control 

cache-control conversation with Akamai:

 

1. if cache-control headers are not used: control is handed over to browsers and proxies in-between.

 

2. Most clients use between no-cache to 1hour (life of a session?).

 

3. Even if no-cache is used, it doesn't impact the cacheablility at Akamai layer, resource will still be served from the edge as configured.

 

4. Currently our sites are configured to pass the cache-control headers from origin thru to user, it can be setup to inject the values we want if we don't want to control it at the apache layer.

 

Side Question: if v2.js is the new version for the release and old page requests it v1.js , will the new version of the app return it or will it return a 404 not found?

does this help/hurt us? Not sure of the relevance here.

 

Based on splunk it looks like we return a 200:

 

index="bwi_grs" NOT "10.136.128.108" uri_path="/etc.clientlibs/example/clientlibs/clientlib-all.min.*.js"  status=200 | timechart count by uri_path