Handle HTTP headers in a more case insensitive way #392
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
|
Ref Issue #391 |
|
@billtomczak Thanks for taking the time to do this! Also, very cool to know that you are using this client with HTTP/2. We might want to consider recommending that to our other users in the future. |
|
Glad I could be of help! Though it wasn't like we had planned the change. We got caught by a random update by our hosting provider that caused a mild panic over here. |
aaron-junot
approved these changes
Jan 8, 2019
This was referenced Jan 17, 2019
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.
Changes Recurly_Client to always force HTTP header keys in to lowercase before storing in Recurly_Response.