Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Output-caching should support ETags #40226

Closed
Tracked by #40232
sebastienros opened this issue Feb 15, 2022 · 0 comments
Closed
Tracked by #40232

Output-caching should support ETags #40226

sebastienros opened this issue Feb 15, 2022 · 0 comments
Assignees
Labels
area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares feature-output-caching
Milestone

Comments

@sebastienros
Copy link
Member

When configured, an eTag header will be generated. If the "If-None-Match" header is defined, a 304 response is returned.
When not configured, eTag values are not generated, and the "If-None-Match" header is ignored.
eTag might be generated on further requests only, to optimize for the first response (pass-through response writing without bufferization).

@sebastienros sebastienros added this to the 7.0-preview5 milestone Feb 15, 2022
@sebastienros sebastienros self-assigned this Feb 15, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Aug 26, 2022
@amcasey amcasey added area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares and removed area-runtime labels Jun 2, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares feature-output-caching
Projects
None yet
Development

No branches or pull requests

2 participants