dotnet/aspnetcore

Cache invalidation

Open

#2,622 opened on Jan 2, 2018

View on GitHub
 (10 comments) (10 reactions) (0 assignees)C# (10,653 forks)batch import
Needs: Designaffected-fewarea-middlewareenhancementfeature-response-cachinghelp wantedseverity-nice-to-have

Repository metrics

Stars
 (37,933 stars)
PR merge metrics
 (Avg merge 16d 9h) (258 merged PRs in 30d)

Description

From @JunTaoLuo on Thursday, September 15, 2016 2:15:48 PM

Currently we only set the absolute timeouts for cache entries. There is no mechanism to explicitly invalidate a cache entry before expiry. Also, how would applications/users interact with this feature?

Note that invalidation is required by the RFC for unsafe methods, e.g. a successful PUT should invalidate any previous cached resources at the same URI.

Copied from original issue: aspnet/ResponseCaching#38

Contributor guide

Research direction
Implement explicit cache invalidation for unsafe HTTP methods (PUT, DELETE, etc.) as per RFC 7234. This requires modifying the response caching middleware to clear cached entries for the request URI on such requests.
Tech stack
csharp
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70