Pages with special characters are not accessible via reverse proxy

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform Notice: Server and Data Center Only - This article only applies to Atlassian products on the server and data center platforms.

(warning)  Atlassian applications allow the use of reverse-proxies within our products, however Atlassian Support does not provide assistance for configuring them. Consequently, Atlassian can not guarantee providing any support for them.

If assistance with configuration is required, please raise a question on Atlassian Answers.


Opening a page with a title that contains special characters leads to a system error.  For example: [ABC] Hello

The following appears on the screen as well as in  atlassian-confluence.log

Caused by: Illegal character in path at index 14: /display/<SPACEKEY>/[ABC]+HELLO
	at com.github.kristofa.brave.servlet.ServletHttpServerRequest.getUri(
	... 49 more



Confluence is configured with an Apache Reverse Proxy, an Apache Reverse Proxy Using the AJP Protocol OR NGINX.


While the handling of special characters in the page title worked for the proxy configuration while running Confluence 5.8.x, the same configuration no longer works in version 5.10.x or higher.


Apache Reverse Proxy Using the AJP Protocol

In the httpd.conf.local file, the following JkOption will most likely be present:

JkOptions +ForwardKeySize +ForwardURICompat -ForwardDirectories

The +ForwardURICompat parameter needs to be changed for Confluence 5.10.x  to +ForwardURICompatUnparsed.  For example:

JkOptions +ForwardKeySize +ForwardURICompatUnparsed -ForwardDirectories

Apache Reverse Proxy

For an Apache reverse proxy, ensure that the following is present:

ProxyPass /confluence http://localhost:8090/confluence nocanon


For NGINX, simply edit the nginx.conf file by adding $request_uri; to the proxy_pass directive (as long as the location and context path are the same).  For example: 

location /<context-path> {

    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Server $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 

proxy_pass http://<base-url>/<context-path>$request_uri;

If this doesn't work or returns an error (we've seen some users receive 502 errors with the above change), then please use the following:

location /<context-path> {

    proxy_set_header X-Forwarded-Host $host;
    proxy_set_header X-Forwarded-Server $host;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; 
if ($request_uri ~* "/<context-path>(/.*)") { 
	proxy_pass http://<base-url>/<context-path>$1; break; 

proxy_pass http://<base-url>/<context-path>;

In all cases, the proxy will need to be restarted to pick up these changes.

Last modified on Aug 27, 2020

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.