litespeedtech / litespeedtech/lsquic
Uppercase field names are allowed
- Dominant language
- C
- Stars
- 1.9k
- Forks
- 397
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 8
Description
[RFC 9114 says](https://datatracker.ietf.org/doc/html/rfc9114#name-http-fields):
> request or response containing uppercase characters in field names MUST be treated as [malformed](https://datatracker.ietf.org/doc/html/rfc9114#malformed).
lsquic only does this in HTTP/1.1 compatibility mode (when `ea_hsi_if` is not specified and thus). Without it, lsquic allows uppercase letters in field names.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing HTTP/3 field-name validation and compare it with the existing HTTP/1.1 compatibility-mode behavior. Add coverage for uppercase field names when ea_hsi_if is not specified, then verify that such requests or responses are treated as malformed while compatibility behavior remains unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100