title: Caching of static assets when index.html gets 304 on second request?
body: <p>I am noticing this behavior and I'm not sure how this works. I have an Nginx Server which doesn't send any caching headers. It only sends E-Tags and Last Modified header. So the second time when I visit the site, the browser sends a request and receives 304 response code from Nginx. After that all static assets from the site are automatically served from the browser cache. I'm not sure why this happens.
  My understanding was for Caching to happen, the server needs to send either Cache-Control headers expires headers with the response, but here without these, the files are still cached.
  Can anyone help me out here?</p>