luckyframework / luckyframework/lucky
HTTP/2 headers should all be lowercase
Nobody has claimed this yet.
- Dominant language
- Crystal
- Stars
- 2.7k
- Forks
- 172
- PR merge metrics
- No merged PRs in 30d
Description
According to the HTTP/2 spec, all headers should be lowercase.
Currently crystal handles checking against lowercase vs uppercase, and dashes vs underscores, so CONTENT_TYPE is the same as content-type. We could safely lowercase, and dasherize for convention any place that we mention a header key directly.
This also makes me curious to know what else we would need to do to ensure we fully support HTTP/2? 🤔
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
No file or test is named. Start by tracing where Lucky checks and emits HTTP header keys, then compare those paths with the HTTP/2 specification linked in the issue. Done means header keys are consistently lowercase and conventionally dasherized without breaking existing header lookups; broader HTTP/2 support is not scoped.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- crystal
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100