Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [jetty-users] Jetty 9 rewriting charset=utf-8 on response headers

Looks like a org.eclipse.jetty.http.HttpGenerator.STRICT property would be the equivalent one for the response headers.

Know that strict behavior will increase memory usage.
Essentially with strict usage, no string portions can be reused, making every request (and now response) effectively churn the GC for no good reason.

Joakim Erdfelt <joakim@xxxxxxxxxxx>
Expert advice, services and support from from the Jetty & CometD experts

On Thu, Oct 17, 2013 at 4:52 AM, Ben Summers <ben@xxxxxxxxxxxx> wrote:


The latest versions of Jetty 9 are rewriting the content-type response headers, turning charset=utf-8 into charset=UTF-8.

It looks like there's some debate over which is "correct", but regardless, I would rather like to maintain the behaviour of our application, and keep the "utf-8" version.

A very similar issue came up before regarding similar rewriting of the request headers, and a org.eclipse.jetty.http.HttpParser.STRICT option was added to turn off an optimisation which caused this behaviour.

Would it be desirable to make this apply to response headers as well?

I've submitted a bug:

Here's the previous bug:




jetty-users mailing list

Back to the top