[Backend] Check if we handle HTTP headers as case-insensitive

Open
#49 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes, typescript
Domain
backend

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.

Description

enhancement

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).

Dominant language
TypeScript
Stars
290
Forks
46
Avg merge
6m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/DurableFunctionsMonitor

All issues in microsoft/DurableFunctionsMonitor

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.