Option to allowlist or blocklist query params
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 166
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
I love the removeUrlQueryParams option, but I have a more nuanced use-case. oauth signed URLs require timestamps, which obviously makes them uncacheable as is. But they also include query params that do need to be part of the cache key. It would be great to have a way to choose which query params were part of the cache key and which were dropped.
Contributor guide
No contributing guide indexed for this repository
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 locating the implementation of the removeUrlQueryParams option and the code that builds cache keys. Trace how query parameters are currently removed, then determine where an allowlist or blocklist setting would apply. Done means callers can choose which parameters remain part of the cache key while signed timestamp parameters can be excluded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100