On 14/01/2020 19:33, Luis Arriaga wrote: > Hi Apache team, > > We are updating our encoding implementation on Tomcat and the ServiceNow > platform from ISO-8859-1 to UTF-8 and ran into some concerns. There is a > URIEncoding property that defaults to UTF-8 if it is not specified. Is > there any reason there is no BodyEncoding property or is there a > workaround you guys are aware of that does not require the source code > to be modified? Looking through the Tomcat source code the default body > encoding seems to be ISO-8859-1, looking at the Parameters, ByteChunk, > and Constants classes there are two variables DEFAULT_BODY_CHARSET and > DEFAULT_CHARSET that determine the body charset/encoding. > > We have forked the Tomcat source code and applied the changes below > which fixed the issue. Are you guys aware of this? Seems strange to have > a URIEncoding property but not a BodyEncoding property unless I am > missing something. Maybe this is an enhancement request we can submit > unless there is a valid reason to not have such property.
Please read the FAQ. https://cwiki.apache.org/confluence/display/TOMCAT/Character+Encoding#CharacterEncoding-Q3 Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
