http - Resource with cache headers still going out -


on call want cached forever, put these headers (from response see):

http/1.1 200 ok x-powered-by    express vary    accept-encoding cache-control   public, max-age=31536000 expires wed, 14 may 2014 21:09:45 gmt last-modified   tue, 14 may 2013 21:09:45 gmt date    tue, 14 may 2013 21:09:45 gmt connection  keep-alive transfer-encoding   chunked 

and yet, when reload page, can see these requests still going out network.
headers should have put prevent calls going out?

thanks

usually when reload page "reload" or "refresh" feature of browser, re-request resources (even if cached).

do see same requests going out if browse page again instead of reload it? e.g. open new tab , enter url of page in question there, should see browser not making request. if still making request can @ browser's settings ensure not configured behave way.

your cache-control header looks good, , behaved browser shouldn't request resource more once unless cache cleared or max age has been exceeded.


Comments

Popular posts from this blog

jquery - How can I dynamically add a browser tab? -

node.js - Getting the socket id,user id pair of a logged in user(s) -

keyboard - C++ GetAsyncKeyState alternative -