Fix/types lowercase response headers #7160
Open
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.
Summary
This PR corrects the TypeScript types for common response headers to use lowercase keys, aligning them with Axios's documented runtime behavior. This solution explicitly addresses the maintainer's feedback on issue #7110 by ensuring the type system correctly handles any header casing.
Problem
At runtime, Axios normalizes all incoming response header keys to lowercase (e.g.,
content-type). However, theCommonResponseHeadersListtype definition used TitleCase keys (e.g.,'Content-Type').This created a discrepancy where TypeScript would incorrectly approve of accessing a TitleCase header, which would be
undefinedat runtime.