Tag Info

So is there a way in S3 to set a dynamic Expires that is always one year from the request date? Not that I know of, and I doubt that dedicated support for this will be considered by the AWS team: You are probably aware that one can't set a dynamic Expires: ... value as such because The only value valid in an Expires header is a HTTP date; anything ...

Caching speeds up repeat views and not first time visits so in terms of SEO value it means little since the first view time is the most important factor. Caching is good however because it means when people switch from page to page they are only loading the resources they need so this will boost user experience. Using no-cache will disable the cache and ...

See http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.3: The max-age directive on a response implies that the response is cacheable (i.e., "public") unless some other, more restrictive cache directive is also present. It's conceivable (likely?) that there are proxies in the wild which break this but since the only failure mode could be ...

I think that it would work although with the amount of time spent, you'd be better off guest blogging, writing press releases and making link bait, etc. As even if you got a pr5 site (I know page rank is not such a good measure nowadays but bear with me) you'd just end up with a load of links coming from one domain. You'd be much better off having them come ...

These headers are used to discourage browsers or proxies from caching the page. For dynamically generated content the headers would be there to try and ensure site visitors are always hitting the server and so are always getting up-to-the minute content. To answer your specific question, these headers may negatively affect performance because they may ...

Without seeing the headers for when you reloaded the page it is a little hard to double check some things. One thing I do notice is that the dates/times don't seem correct (though this may just be an artefact of how you copied and pasted your question). The response from Google's server says the Date is Thu, 01 Mar 2012 20:58:10 GMT while your js says it ...