Summary: | Breaking change in Content-Type / Character Encoding handling | ||
---|---|---|---|
Product: | Tomcat 8 | Reporter: | Matthew Shaw <matthew> |
Component: | Catalina | Assignee: | Tomcat Developers Mailing List <dev> |
Status: | RESOLVED FIXED | ||
Severity: | regression | ||
Priority: | P2 | ||
Version: | 8.5.15 | ||
Target Milestone: | ---- | ||
Hardware: | All | ||
OS: | All |
Description
Matthew Shaw
2017-06-19 00:19:34 UTC
The change relates to this entry in the change log: <quote> 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) </quote> 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. Fixed in: - trunk for 9.0.0.M22 onwards - 8.5.x for 8.5.16 onwards |