502 gateway error if length of content-type for header for http more than 256k
Open
Nobody has claimed this yet.
invalid
- Dominant language
- C
- Stars
- 31.7k
- Forks
- 8.3k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 13
Description
Describe the feature you'd like to add to nginx
A clear and concise description of the feature.
Describe the problem this feature solves
A clear and concise description of the problem.
Additional context
Add any other context about the feature request here.
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
The issue names no files, tests, or entry points and provides only a vague title plus an unfilled feature template. Start by reproducing the 502 with a Content-Type header over 256k and tracing the request through NGINX's HTTP header handling. Done means the expected behavior and the cause of the gateway error are specified and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, nginx
- Domain
- backend, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100