Hacker News Reader

Firefox won’t reload the resource, even if the page the resource is on is POSTed to.

Use case: Logging into Facebook, previously browsers reloaded all resources.

You typically do a 302 redirect AFTER the POST authentication. This feels more of a publicity stunt more than anything. It might affect very few use-cases. Bulk of the requests on the web are GETs anyway.

I agree. Facebook redirects a successful login POST with a 302, which then results in a GET to '/'. This is an extremely common pattern. Once you're making GETs, 'fresh' resources can be served from cache without revalidation [1]. This is basically the whole point of the fresh vs. stale distinction.

[1] https://tools.ietf.org/html/rfc7234#section-1

Why would the browser need to reload all resources after a POST request?

Presumably, only the main (HTML) page should be refreshed and other linked items (CSS/JS/media) with high max-age (and no 'must-revalidate' cache control header) should use the previously cached content.

Reply on news.ycombinator.com