As far as I understand, when a request is made for the very first time, the browser will download the resource from the server.
header is present, then it can cache it for
This much is clear.
max-ageset, in the second request for the same resource, why is there a
Responseshowing in the profiler? Technically there shouldn't be a
Responseright? Is it from the
resource cache? Assuming that it is a pseudo response from the clients caching mechanism, should that
Cache-Controlheader or not (remember the first request already informed that)?
no-cachein the request and it gets a response with
max-age, how does that work for the next request? Will it do a round-trip to check if the content has not changed? How about server using
max-agetogether - is that possible?
Cache-Control: private,max-age=86400header. However, in this scenario, I see that there was a
Etagin the previous response and client sends it back in
If-None-Matchin the next request and the HTTP response is
304. Is that normal?
I am trying to troubleshoot a
cache issue in
IE 11 where despite the
Cache-Control: private,max-age=86400 in the
Response Header, the content is still downloaded from the server. There is a
Cache-Control: no-cache in the
Request Header though.
It happens when we browse normally as well as with the
F12 Developer Tools.
Our Network Topology is something like
Client <-> F5 <-> App Server.
I am also reading the HTTP Caching article in Google Developers but things are not so clear.