caddyserver / caddyserver/cache-handler
Header normalization
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 393
- Forks
- 28
- Avg merge
- 32m
- Merged PRs (30d)
- 1
Description
Hi, I'm looking for some guidance on Accept-Language and Accept-Encoding header normalization to avoid high cache key cardinality.
For encoding, I was thinking of something like:
map {header.Accept-Encoding} {accept} {
~br br
~gzip gzip
default *
}
request_header Accept-Encoding {accept}
And for Accept-Language I was looking at https://github.com/simia-tech/caddy-locale but it doesn't seem to work with caddy 2.
Do you have recommendations? Is this even necessary?
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
No repository files, tests, or entry points are mentioned. Start by locating the cache-key handling relevant to HTTP headers, then determine whether Accept-Encoding and Accept-Language normalization is needed and document the agreed scope or recommendation.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100