Remove charset from "Content-Type" header

[Pandazaur]

Hello,

I need to post some data to a distant API. But it looks like the API wants Content-Type: application/json but I'm sending a Content-Type: application/json; charset=utf-8.

I forced the headers:

Map<String, String> headers = {
            HttpHeaders.AUTHORIZATION: 'Bearer ${this._token}',
            HttpHeaders.CONTENT_TYPE: 'application/json'
};

but keep sending with the charset. Is there a possibility to remove it from the Content Typeheader ?

Thanks

Looks like charset ("encoding") is always added on Content-Type in case it's not set:
https://github.com/dart-lang/http/blob/master/lib/src/request.dart#L84-L92

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:
https://tools.ietf.org/html/rfc2045#section-5

As far as I can tell the 'application/json' MIME type does explicitly not define a "charset" parameter:
https://www.iana.org/assignments/media-types/application/json

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.

[jheyne]

Work-around: Set the body first (this sets default headers), then set the headers.

[jefioliveira]

I have the same problem, however the above solution did not work in my case.

[jheyne]

For clarity, this is what worked for me:
Request request = new Request('POST', Uri.parse(url));
request.body = body;
request.headers['content-type'] = 'text/xml';
request.headers['accept'] = 'text/xml';

[aloisdeniel]

I encountered the same issue, but @jheyne workaround didn't work for me.

We should be able to write request.encoding = null.

[cmregazzo]

Good afternoon,

I have the same problem.

The lib is automatically placing charset = utf-8 in the request header, so I'm having trouble consuming some REST WebServices, making it impossible to use it.

The issue is already open for one year.

Is there no solution to such a problem?

Thank you.

Cristian Regazzo

[Dudecor3]

Has anyone solved this yet?

It seems to be more of a problem when there encoding more complex types such as

class MyClass { ClassOne class1; ClassTwo class2; }

I've tried jsonEncode, I've used the JSONSerializable package, setting the body before headers, just as @jheyne mentioned. I don't understand why the HttpClient encodes to UTF-8 by default. Either way, life is very difficult right now. I've even added UTF-8 encoding to my .NET server and still nothing :(

Marc