Caching and sizes, the explosion of responise codes (was Re: Caching and status codes)
Zach DeCook
zachdecook at librem.one
Sun Nov 8 06:08:19 GMT 2020
On November 8, 2020 12:59:09 AM EST, Sudipto Mallick <smallick.dev at gmail.com> wrote:
>It is assumed that requests with query part ...
That client-implementation could lead to strange uses of the query part...
But if it's a result of a 10 or 11 response, it would make sense to make the request fresh.
mbays at sdf.org is right, the user should be in control.
A caching client could simply split links to cached resources into two parts: clicking one part would pull the cached version, clicking the other would make a new request.
-Zach
More information about the Gemini
mailing list