This is what I *think* how *should* clients work with caching: The clients with history support and supports going ''backwards'' and ''forwards'' through history should cache text/* responses in memory for that browsing session. When the user browses through the history using ''forward'' and ''backward'' action, no reloading should happen. But, when a user clicks the link for a resource already in cache or writes the link by hand or selects the link from previously visited links or asks for reload: the cache is purged and the resource reloaded. It is assumed that requests with query part are idempotent. Now, when a page is dynamic, it should be stated as such so that the user would reload that page. With that, no new response codes. ~smlckz
---
Previous in thread (30 of 55): 🗣️ Zach DeCook (zachdecook (a) librem.one)
Next in thread (32 of 55): 🗣️ Zach DeCook (zachdecook (a) librem.one)