Requests with application/json Content-Type do not correctly assume UTF-8 charset

• Framework version: 1.1.1 - 1.1.3
• Implementations: All

Scenario

It seems that the changes for #150 broke the assumption that all JSON is UTF-8, by definition.

Expected behavior

Parsing a JSON request body to a Java type should assume UTF-8 charset.

Actual behavior

It does not correctly handle characters out of ascii set.

Steps to reproduce

Send request with appplication/json in the Content-Type header and strange characters such as » in the JSON body. It will not be correctly parsed and throw a bad request.

If you set the Content-Type header to application/json; charset=UTF-8 then it works fine, but should not be necessary and most REST clients won’t do it.

Full log output

Invalid UTF-8 middle byte 0x65\\n at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream); line: 1, column: 13]\\n at [Source: (org.glassfish.jersey.message.internal.ReaderInterceptorExecutor$UnCloseableInputStream);

Thanks for your support!

[sapessi]

Perhaps I could add a field for this in the ContainerConfig object, default it to ISO-8859-1, but give you the ability to change this whenever you want:

LambdaContainerHandler.getContainerConfig()
    .setDefaultContentCharset(StandardCharsets.UTF_8.name())

Thoughts?

[sapessi]

That’s the plan.