http - max-age, no-Cache,must-revalidate on Cache-Control Header, Which takes predence here? -


cache-control : max-age=86400, no-store, must-revalidate, no-cache

this response header set server js file.

does mean response cached 86400 seconds before revalidating?.

which of above 1 takes precedence , resiult?.

looks no-cache give precedence on all. http1.1 specification says "if no-cache directive not specify field-name, cache must not use response satisfy subsequent request without successful revalidation origin server." refer http://www.w3.org/protocols/rfc2616/rfc2616-sec14.html#sec14.9.1

it says "the max-age directive on response implies response cacheable (i.e., "public") unless other, more restrictive cache directive present. " refer http://www.w3.org/protocols/rfc2616/rfc2616-sec14.html#sec14.9.3

all above http/1.1 .


Comments

Popular posts from this blog

java - Plugin org.apache.maven.plugins:maven-install-plugin:2.4 or one of its dependencies could not be resolved -

Round ImageView Android -

How can I utilize Yahoo Weather API in android -