> On Nov 5, 2020, at 9:52 PM, bie <bie at 202x.moe> wrote: > > Now, I don't see the need for caching at all when it comes to > gemini, but if it's something the gemini community wants or needs then > I'd like to suggest a 2x status code that let's a client know that the > response is unlikely to change and thus cacheable. This could even kind > of match how the temporary/permanent redirect status codes are defined: > > 20 - SUCCESS > 21 - "PERMANENT" SUCCESS (Feel free to cache this) Bit of a bikeshed comment, but ?permanent success?, especially the ?permanent? part, makes me think of Cache-Control: immutable. That is, the server is claiming that the file will not change, ever. (Gemini doesn?t have conditional revalidation.) https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control
---
Previous in thread (19 of 55): 🗣️ khuxkm (a) tilde.team (khuxkm (a) tilde.team)