Skip to content

Output-caching entries can be purged programmatically #40228

New issue
New issue
Closed
Listed in
#40232
#41037
Closed
Output-caching entries can be purged programmatically#40228
Listed in
#40232
#41037
Assignees
sebastienros
Labels
area-middlewareIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresfeature-output-caching
Milestone
 
7.0-preview6
@sebastienros

Description

@sebastienros
sebastienros
opened on Feb 15, 2022

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.

Activity

sebastienros
added
area-runtime
feature-output-caching
on Feb 15, 2022
sebastienros
added this to the 7.0-preview4 milestone on Feb 15, 2022
sebastienros
self-assigned this
on Feb 15, 2022
sebastienros
mentioned this on Feb 15, 2022
sebastienros
mentioned this on Apr 4, 2022
adityamandaleeka
modified the milestones: 7.0-preview4, 7.0-preview5 on Apr 20, 2022
sebastienros
modified the milestones: 7.0-preview5, 7.0-preview6 on Jun 6, 2022
wtgodbe
closed this as completedin #41037on Jun 22, 2022
ghost locked as resolved and limited conversation to collaborators on Jul 23, 2022
amcasey
added
area-middlewareIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewares
and removed
area-runtime
on Jun 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area-middlewareIncludes: URL rewrite, redirect, response cache/compression, session, and other general middlewaresfeature-output-caching

Type

No type

Projects

No projects

Milestone

Relationships

None yet

    Development

    Participants

    @adityamandaleeka@sebastienros@amcasey

    Issue actions
      Output-caching entries can be purged programmatically · Issue #40228 · dotnet/aspnetcore