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.

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

fix: do not manually parse content-type #20538

merged 1 commit into from Oct 11, 2019


Copy link

@zcbenz zcbenz commented Oct 11, 2019

Description of Change

Close #20182.

This PR fixes invalid mime type being set caused by manually parsing the content-type header.


Release Notes

Notes: Fix setting content-type header with charset breaking protocol APIs.

@jkleinsc jkleinsc merged commit 1b2c6a3 into master Oct 11, 2019
16 checks passed
Copy link

@release-clerk release-clerk bot commented Oct 11, 2019

Release Notes Persisted

Fix setting content-type header with charset breaking protocol APIs.


@jkleinsc jkleinsc deleted the fix-content-type-charset branch Oct 11, 2019
Copy link

@trop trop bot commented Oct 11, 2019

I have automatically backported this PR to "7-0-x", please check out #20544


Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked issues

Successfully merging this pull request may close these issues.

3 participants