microsoft / microsoft/DurableFunctionsMonitor
[Backend] Check if we handle HTTP headers as case-insensitive
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 290
- Forks
- 46
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Description
According to the standard, HTTP header names are case-INsensitive.
As it turned out, some environments (by which I mean Kubernetes) may treat this literally and convert response header names to lower case on-the-fly.
Need to check whether we handle this case correctly (spoiler: most likely not).
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 files, tests, or entry points are named. Start by locating the backend response-header handling and check its behavior with mixed-case and lower-case header names, then add coverage showing that Kubernetes-style lower-cased headers are handled correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100