Makes response header references case insensitive #149
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dbrudner
requested review from
douglasmiller,
cainj,
chrissrogers and
joannasese
dbrudner
force-pushed
the
normalize-response-headers
branch
from
2849d66
to
d5c0a39
Compare
dbrudner
force-pushed
the
normalize-response-headers
branch
from
d5c0a39
to
fcf6012
Compare
douglasmiller
added a commit
that referenced
this pull request
Oct 8, 2020
# Changelog ## [Unreleased](https://github.com/recurly/recurly-client-node/tree/HEAD) [Full Changelog](3.14.0...HEAD) **Fixed bugs:** - Makes response header references case insensitive [\#149](#149) ([dbrudner](https://github.com/dbrudner))
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
All response headers previously were being accessed through lowercase values with the exception of
Recurly-Sunset-DateandRecurly-DeprecatedPager/list methods are working fine with the current release. The update here is for the purpose of fixing the two above headers and future-proofing.