3 ms·

I'm not exactly sure why browsers do that, but I suspect that's due to caching. However, I would suggest that you use "Inspect element" and open up dev tools -

• aplummer 10y ago
  Often the dom has been changed, and you want to know what the server actually sent
  • jbm 10y ago
    You can still do that with the inspect menu; if you look at the network history in Chrome, you can see the headers sent, the headers received and the body sent / received.
    • koolba 10y ago
      > You can still do that with the inspect menu; if you look at the network history in Chrome, you can see the headers sent, the headers received and the body sent / received. That only works if you have it open before the page loaded. It doesn't save information about network requests that occurred before the inspector was opened.
      • noir_lord 10y ago
        It would be handy if it did though since I continually forget to open inspector before the request. I'd love a "I'm a developer, store all the things!" setting
• radarsat1 10y ago
  > I suspect that's due to caching. Shouldn't caching have the opposite effect? i.e. it's treated as a new resource but no new http request is needed because it's in the cache..