Title: I&#x27;ve noticed that both Firefox and Chrome issue a new HTTP request when you view the source for a web page that you&#x27;ve already loaded. It&#x27;s particularly annoying when the page itself is slow to load or if it won&#x27;t load at all.<p>Why is that? Wouldn&#x27;t they have the existing source for the originally received page cached already? Is it based on Cache-Control headers?<p>This has been on my mind for a while (usually comes up when looking at what&#x27;s behind slow web apps) and came up again with Piwik on the front page[1]. Their website was semi-down (HN hug of death) but eventually loaded. I wanted to see what their GA equivalent tracking code looks like but the page failed to load as rather than showing the cached copy, it tried to fetch a new one.<p>[1]: https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=13210195
Upvote: