'charse=null' is automatically added randomly using 'application/problem+json' in ServletApiResponse.

[isanghaessi]

Jetty version(s)
12.0.8

Jetty Environment
ee10

Java version/vendor (use: java -version)
JDK17 / temurin

OS type/version
Mac / Sequoia 15.5

Description
I was debugging Spring-Framework issue.
I think Jetty's ServletApiResponse has a bug.

In summarize,
ServletApiResponse add 'charset=null' when set Content-Type following order.

• application/json
• null
• application/problem+json

How to reproduce?
In the following order, set Content-Type.

• application/json
• null
• application/problem+json

Here's origin issue from Spring-Framework.
spring-projects/spring-framework#35087

[janbartel]

@isanghaessi I don't think this problem exists in 12.0.21, but please test in your environment.

[isanghaessi]

@janbartel
I tested with version 12.0.21, still got same response.

[janbartel]

@isanghaessi ah yes, I see the problem. I'm sorry, I assumed the issue was the use of the application/problem+json, but I see now it is a combination of factors: an inferred charset from the application/json, removing the Content-Type header, and then using a Content-Type that has no charset, inferred or otherwise. Working on a fix.

[isanghaessi]

@janbartel
thanks for answer and work!