Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Updating client to be compliant with RFC 2616: case-insensitive headers #556

Merged
merged 2 commits into from
Oct 1, 2020
Merged

Updating client to be compliant with RFC 2616: case-insensitive headers #556

merged 2 commits into from
Oct 1, 2020

Conversation

douglasmiller
Copy link
Contributor

According to section 4.2 of RFC 2616:

Each header field consists of a name followed by a colon (":") and the field value. Field names are case-insensitive.

This update will make the client treat headers in a case-insensitive manner.

@douglasmiller douglasmiller added bug V2 V2 Client labels Oct 1, 2020
@joannasese
Copy link
Contributor

Please add changelog update

@dbrudner dbrudner merged commit f60e924 into release_2_10 Oct 1, 2020
@dbrudner dbrudner deleted the 2-10-headers branch October 5, 2020 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@chrissrogers chrissrogers Awaiting requested review from chrissrogers

@cainj cainj Awaiting requested review from cainj

@joannasese joannasese Awaiting requested review from joannasese

Assignees
No one assigned
Labels
bug V2 V2 Client
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

None yet
3 participants
@douglasmiller @joannasese @dbrudner