New middlewares for various client cache methods that can speed your pages even more #935
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cleanup of some old code: 46846d5
Add new handlers for client (i.e browser) caching:
cache.NoCache
andcache.StaticCache
including tests by @speedwheel via PR: Add some useful cache middlewares for client (i.e browser) catching #934Add one more browser (and 304 server) cache method using ETag and If-None-Match headers and replace the
ctx.WriteWithExpiration
with simplectx.Write
atStaticEmbeddedHandler
of core/router/fs.go, now that we have plenty of options for client cache give the end-dev the oportunity to use them or not on static embedded handlers: 16c473a