Json Content-Type and explicity encoding declaration

[MichelFortes]

Like the Spring developer team has done, it would be interesting to consider that all content-type "application/json" responses where encoded with UTF-8 charset.

From Spring Team:
/**
* A String equivalent of {@link MediaType#APPLICATION_JSON_UTF8}.
* @deprecated as of 5.2 in favor of {@link #APPLICATION_JSON_VALUE}
* since major browsers like Chrome
*
* now comply with the specification and interpret correctly UTF-8 special
* characters without requiring a {@code charset=UTF-8} parameter.
*/
@deprecated
public static final String APPLICATION_JSON_UTF8_VALUE = "application/json;charset=UTF-8";

[pierrediderot]

+1.

[natebosch]

Closing in favor of #175

The expected pattern to use today when you know the result is json is jsonDecode(utf8.decode(response.bodyBytes)). We should consider changing the default decoding so that fewer users get confused by this.

[DeD1rk]

@natebosch you linked the wrong issue, also in another issue.

[natebosch]

@DeD1rk - corrected. Thanks for the heads up!