1. HTTP, by definition, works as a stateless request/response protocol. Distinguishing between reload (re-requesting the current page) and "simulated reload" re

1. HTTP, by definition, works as a stateless request/response protocol. Distinguishing between reload (re-requesting the current page) and "simulated reload" requires maintaining state. Browser caching can violate the stateless nature of HTTP, if the web site allows it to, but the user can still force-reload to bypass caching. 2. The user controls their browsing. Web apps that hijack navigation, history, or reloading take control away from the user. In any case service workers can already do this, as another commenter mentioned.