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

Standardize Content-Type capitalization #146

Merged
merged 3 commits into from Sep 11, 2014

Conversation

Projects
None yet
2 participants
@jimhester
Member

jimhester commented Sep 8, 2014

While apparently the header fields are supposed to be case insensitive,
#142 shows at least some systems do not follow the spec properly. So
we might as well standardize all uses of Content-Type in the same
way.

@hadley

This comment has been minimized.

Member

hadley commented Sep 9, 2014

Could you please also add a note to NEWS?

jimhester added some commits Sep 8, 2014

Standardize Content-Type capitalization
While apparently the header fields are supposed to be case insensitive,
 #142 shows at least some systems do not follow the spec properly.  So
we might as well standardize all uses of `Content-Type` in the same
way.

@jimhester jimhester force-pushed the jimhester:Content-Type branch from 3a36415 to d4da653 Sep 9, 2014

@jimhester

This comment has been minimized.

Member

jimhester commented Sep 9, 2014

Added note to news and rebased on the current master. In the first pull request I had neglected to update the remote, sorry!

Fix broken merge
There was an extra block I missed when I was doing the merge
@jimhester

This comment has been minimized.

Member

jimhester commented Sep 9, 2014

Ok this should be good after travis passes, I missed a block when I was fixing merge conflicts the first time.

hadley added a commit that referenced this pull request Sep 11, 2014

Merge pull request #146 from jimhester/Content-Type
Standardize Content-Type capitalization

@hadley hadley merged commit 397fd08 into r-lib:master Sep 11, 2014

1 check passed

continuous-integration/travis-ci The Travis CI build passed
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment