Size constraints for cache names?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 3.6k
- Forks
- 324
- Avg merge
- 14d 22h
- Merged PRs (30d)
- 1
Description
Currently the spec seems to allow arbitrary (multi-MB?) long cacheNames passed to the various CacheStorage methods. Would it make sense to spec some upper limit for what browser should support regarding size of cache names (and specifying what exception to throw if that size is exceeded)?
(related to https://crbug.com/837478 where our fuzzer figured out that passing really long cache names causes chrome to kill the renderer)
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
Start by reading the CacheStorage methods mentioned in the issue and the related Chromium report at crbug.com/837478. Determine whether the specification should define a maximum cache-name size and which exception applies when it is exceeded; the work is done when the required spec change is agreed and clearly scoped.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100