You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Sep 10, 2019. It is now read-only.
HTTP Caching is technically just adding a header, making it relatively easy to implement, but, it might be nice to make it more explicit.
The default should be off, because there might be pages that should never be cached (I'm thinking about Storyteller here, because that's our base platform, and pretty much everything that isn't the FileHandler shouldn't have caching), but making it nicer/easier to use could be useful.
I don't know if this is a good idea, or if we should just say "use the headers map" (wait, do we have a headers map?).
HTTP Caching is technically just adding a header, making it relatively easy to implement, but, it might be nice to make it more explicit.
The default should be off, because there might be pages that should never be cached (I'm thinking about Storyteller here, because that's our base platform, and pretty much everything that isn't the FileHandler shouldn't have caching), but making it nicer/easier to use could be useful.
I don't know if this is a good idea, or if we should just say "use the headers map" (wait, do we have a headers map?).
Links and Such
The text was updated successfully, but these errors were encountered: