This repository has been archived by the owner. It is now read-only.
Handle application/json & text/json #2
Closed
Conversation
…le, Flickr and Yahoo LOVE to send on JSON bodies.)
|
Any concrete examples of the wrong mime type being served? |
|
Flickr API
Google Social API
Google Search API
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Google, Flickr and Yahoo seem to LOVE sending
text/javascriptrather than correctly setting the mime-type… I've commonly seentext/plain, which is even worse—but we can't deal with any situation.Being that this library is a "it should just work when I make a request" affair, I feel that this patch is aligned to your thinking.
What do you think?