Chrome does not cache images / js / css

Question

When Chrome loads my site, it checks the server for updated versions of files before it shows them. (Images / Javascript / CSS) It gets 304 from the server, because I never edit external javascript, css or images.

I want it to display images without even checking the server.

Here are the headers:

Connection:keep-alive Date:Tue, 03 Aug 2010 21:39:32 GMT ETag:"2792c73-b1-48cd0909d96ed" Expires:Thu, 02 Sep 2010 21:39:32 GMT Server:Apache/Nginx/Varnish 

How can I make the server not check the server?

Answer 1

What do the headers of your queries look like?

Chrome will set max-age: 0 in the header of the Cache-Control request if you press Enter in the location bar . If you visit your page with a hyperlink, it should use the cache as expected.

Answer 2

Something that bothered me was ... I had a "disable cache" in the developer tools. Hover over your mouse.

Answer 3

Wow! I have encountered the same problem for quite some time.

I will tell you why you came across this problem. Your headlines are fine. You get 304 because of how you try to refresh the page. There are basically 3 ways -

• Press enter in the address field. You will see that chrome first reads the file from the cache and does not go to the server at all.

• Press f5, this will confirm that the file is out of date (perhaps this is how you update)

• Press Ctrl + f5, this is an unconditional reboot of all static resources.

So, basically - you have to press the return key in the address bar. Let me know if this works.

Answer 4

For me it was a self-signed certificate:

https://code.google.com/p/chromium/issues/detail?id=110649

Chrome does not cache resources from servers with a self-signed certificate.

Answer 5

If you want Chrome to cache your JS / CSS files, the server needs to set the "Cache-Control" header. It should look like this:

Cache-Control: max-age = 86400 (if you want to cache resources for a day).

Answer 6

I believe what you are looking for

Cache-Control: immutable