Skip to content

Content-Type header value not possible to change #35

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
Closed
gramic opened this issue Mar 7, 2011 · 3 comments
Closed

Content-Type header value not possible to change #35

gramic opened this issue Mar 7, 2011 · 3 comments
Labels
BUG HTTP

Comments

@gramic
Copy link

gramic commented Mar 7, 2011

I tried with clear_headers, then adding the header with different value, like "application/json". It adds the header with the same key "Content-Type" twice and never removes the original "x-application/octet-stream".
@ghost
Copy link

ghost commented Mar 7, 2011

This is a bug, and I think I know where to fix it. Please stay tuned.

@ghost
Copy link

ghost commented Mar 7, 2011

This is fixed on 0.9-devel with commits a623730 and 862f614.

@ghost
Copy link

ghost commented Mar 7, 2011

This is also already in 0.8-devel, back-ported from 0.9-devel (same commits).

ghost pushed a commit that referenced this issue Apr 9, 2011
@deanberris
Fixes #35
a623730 
Making calls to client.post and client.put smarter with the provided request objects.
ghost pushed a commit that referenced this issue Apr 9, 2011
@deanberris
Addendum to #35
862f614 
This fix improves upon the earlier commit to make the implementation more predictable
and semantically consistent with the interface for both the put and post methods.
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
BUG HTTP
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gramic