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 entries can be purged programmatically #40228

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

Output-caching entries can be purged programmatically #40228

sebastienros opened this issue Feb 15, 2022 · 0 comments · Fixed by #41037
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

Cached entries can be purged using a service. No default remote support is provided, and each application can define secure endpoints to allow for purging entries remotely.
Entries can be purged by keys or tags.

@sebastienros sebastienros added this to the 7.0-preview4 milestone Feb 15, 2022
@sebastienros sebastienros self-assigned this Feb 15, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Jul 23, 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

Successfully merging a pull request may close this issue.

4 participants
@adityamandaleeka @sebastienros @amcasey and others