Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Remove charset from WebOb JSON exceptions #237
There are no optional/required parameters for
What spec allows alternate encodings? The JSON spec allows UTF based encodings, and knows which it is based upon the first 4 bytes of the JSON response, but this is based upon parsing the JSON content itself, and not based upon the
Okay so a compliant parser should ignore the options then, right? As per the note in that link. Thanks for linking to the media type, I wasn't aware it didn't have any optional parameters. Regardless, I guess the fact that webob has a charset is a little odd since it only applies to some media types.
Yes, a compliant parser will ignore it.
Currently the charset is automatically set on a Response when the user provides a content type of
Now when a user sets the content_type on a Response object using
I should be able to create a Response object without having to override multiple defaults before modifying it to be "my own".