To add to Francis' answer, browsers might not respect server specification
for expiration.
must-revalidate however forces the browser to check the expiration of the
resource before attempting of really load it again from the server.
Read: https://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec
Hello!
On Thu, Jun 30, 2016 at 12:02:29AM +0200, d...@whocaresabout.de wrote:
> currently I am serving files with a size about 1,5G (static without dynamic
> content) using a hand full of nodes and nginx in reverse proxy setup.
> Caching works, ..but not as expected. During the requests nginx cre
On Thu, Jun 30, 2016 at 10:45:31AM +0200, Daniel Eschner wrote:
Hi there,
> i need to understand the caching options better. So, i have serval Questions
> ;)
I think in this mail, you refer to the caching done by your browser.
That is entirely controlled by your browser; but it will probably r
Hi there,
i need to understand the caching options better. So, i have serval Questions ;)
I added some Cacherules like these:
location /js {
add_headerCache-Control public;
add_headerCache-Control must-revalidate;
expires
On Wed, Jun 29, 2016 at 09:00:02PM -0400, blue.outrigger wrote:
Hi there,
> I am using nginx as a reverse proxy and using the proxy-cache, I use the
> request body as a cache key as shown below.
> proxy_cache_key "$scheme$host$request_uri|$request_body";
http://nginx.org/r/$re
