Reflecting the case-insensitivity of http headers #275
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.
I recently went on a really unfun yak-shaving expedition when I:
PATCH
http methodHttpURLConnection
stuff just doesn't support thatHTTPClient
stuff in java 11HTTPHeaders
only reports lower-case header names, even though we're confident that the service returns mixed-case. This broke thechunked
transfer-encoding stuff that theHttpMsg
types do, and required a bunch of tedious test-data updates.HTTPHeaders
's casing behaviour is the correct position, so we're going to adapt to that.