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 <[email protected]> webtide.com <http://www.webtide.com/> - intalio.com/jetty Expert advice, services and support from from the Jetty & CometD experts eclipse.org/jetty - cometd.org On Thu, Oct 17, 2013 at 4:52 AM, Ben Summers <[email protected]> wrote: > > Hello, > > 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: https://bugs.eclipse.org/bugs/show_bug.cgi?id=418888 > > Here's the previous bug: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=414449 > > Thanks, > > Ben > > > -- > http://bens.me.uk > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
