tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 61197] Breaking change in Content-Type / Character Encoding handling
Date Mon, 19 Jun 2017 16:50:09 GMT

--- Comment #1 from Mark Thomas <> ---
The change relates to this entry in the change log:

Start to switch to using Charset rather than String to store encoding
configuration settings to reduce the number of places the associated Charset
needs to be looked up. (markt)

The primary drivers for the change were performance (the repeated String ->
Charset calls were relatively expensive) and earlier error reporting when an
invalid value was provided.

There might be an alternative way of setting the charset that avoids this
restriction. I'll take a look. If that doesn't work, preserving the user
provided value is another option.

You are receiving this mail because:
You are the assignee for the bug.
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message