fix: correct response headers TypeScript types to use lowercase keys [Hacktoberfest] #7110
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
e-headers-lowercase-typing
Suggested PR Description:
Summary
Fix response headers TypeScript types to use lowercase keys matching
runtime behavior.
Problem
Response headers are normalized to lowercase at runtime (as documented),
but TypeScript types incorrectly used Title Case headers, causing
type/runtime mismatches.
Solution
Change
CommonResponseHeadersList
to use lowercase header names:'Server'
→'server'
'Content-Type'
→'content-type'
'Content-Length'
→'content-length'
Test case