Character Encoding Issue Due to Enabled Request Dumper Valve in Tomcat
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
When running the encoding test, gibberish characters are shown (Iñtërnâtiônà lizætiøn), as can be seen in the following screenshot. The encoding test fails in the first test (i.e form submission).
Cause
The Request Dumper Valve option in Tomcat's server.xml is enabled. From Apache documentation, Request Dumper Valve has some side-effects:
The output from this valve includes any parameters included with the request. The parameters will be decoded using the default platform encoding. Any subsequent calls to request.setCharacterEncoding() within the web application will have no effect.
Resolution
Open
server.xmlin<confluence-install>/conffolderComment out or delete the following line:
1<Valve className="org.apache.catalina.valves.RequestDumperValve"/>Restart Confluence
Was this helpful?