Cache and Proxy information
Open
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 135
- Forks
- 40
- PR merge metrics
- No merged PRs in 30d
Description
As discussed at TPAC, exposing information in response headers from caches and intermediaries would help measure CDN and other intermediary performance on an apples-to-apples / real user measurement basis.
(working on a PR now)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file, test, or entry point. Read the TPAC discussion and the current Resource Timing specification first, then determine the intended response-header information for caches and intermediaries and how it should be exposed for comparable performance measurement. The issue is marked as having a PR in progress, so confirm the current work before starting.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100