• Content Type Response Header

Content Type Response Header

Looks like charset ('encoding') is always added on Content-Type in case it's not set: For good measure I checked with the RFCs and it seems the 'parameter' part of the Content-Type value is either mandatory or optional depending on the particular MIME type/subtype: As far as I can tell the 'application/json' MIME type does explicitly not define a 'charset' parameter: Ultimately this points to the http package being buggy. I don't think it's valid to blindly add parameters to just any MIME type. In fact, while probably done with good intentions, silently adding anything should probably be avoided.