HTTP "Expires" header does not work in Chrome

Viewed 9663

My system is Windows 7 x64, Chrome 20.0.1132.57 m.

In my HTTP response header, I have:

Cache-Control: public, max-age=1000
Expires: *some date*

In IE & FF, the page is cached in local, and when I try to access again by typing the URL and hit enter, no request is send and the page is displayed correctly. But in Chrome, it always send a request to the server with the following header:

Cache-Control: max-age=0

I do not want the client send a request to my server and then reply 304. I want to save the round-trip time.

2 Answers
Related