Remove mime-type validation. At least browser clients don't seem to s… #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…et this in a very predictable way, meaning currently browsers cannot use a TJSON endpoint.
trustin
added a commit
that referenced
this pull request
Dec 1, 2015
Remove mime-type validation. At least browser clients don't seem to s…
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…et this in a very predictable way, meaning currently browsers cannot use a TJSON endpoint.
It should be reasonable to assume that server/client set their default serialization format appropriately when mime-types are not recognizable and otherwise there'll be decode/encode errors which can clue into the mismatch (this was the behavior before we added content-type detection).