envoyproxy/envoy

CacheFilter: Support customizing whether to cache responses with no cache-control directives

Open

#9,834 opened on Jan 25, 2020

View on GitHub
 (0 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/cachehelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

RFC7231§6.1 permits caching some responses to GET/HEAD requests without explicit cache-related headers, depending on the status code. To prevent unpleasant surprises, it should be configurable whether CacheFilter (#7198) caches such responses or whether it requires a positive indication of cacheability.

Contributor guide

Research direction
Analyze RFC 7231 §6.1 status codes that permit caching without explicit cache control. Then modify CacheFilter to add a configuration option to toggle caching of such responses.
Tech stack
c
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitC++ basicsHTTP caching conceptsEnvoy proxy architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60