Skip to content

Fix lowercase "content-type" was ignored #101

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

nangchan
Copy link

When specifying the header Content-Type, only uppercase "Content-Type" works but lowercase "content-type" is ignored and overridden by g:vrc_header_content_type.

Solution:
When the user specifies "content-type" the plugin will automatically uppercase to "Content-Type" to match the existing logic.

@riccione
Copy link

riccione commented May 9, 2024

Check Michael Potter pull request 3179c79

Header names are not case sensitive.

From RFC 2616 - "Hypertext Transfer Protocol -- HTTP/1.1", Section 4.2, "Message Headers":

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

The updating RFC 7230 does not list any changes from RFC 2616 at this part.
https://stackoverflow.com/a/5259004

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

Successfully merging this pull request may close these issues.

2 participants