"Invalid character found in the request target" when viewing RSS feeds

[Rilwan Ahmed]

In Confluence 6.11.2,  clicking on any RSS feed in Space Tools > Content Tools > RSS Feed throws the below Error.

HTTP Status 400 – Bad Request

---

Type Exception Report

Message Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986

Description The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

Exception

java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986
	org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:467)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:294)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:770)
	org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2336)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.lang.Thread.run(Thread.java:748)

Note The full stack trace of the root cause is available in the server logs.

Workaround provided in https://jira.atlassian.com/browse/CONFSERVER-57582  DOESNOT resolve the issue

[Diego]

Hello there Rilwan!

Would it be possible for you to share and excerpt of your server.xml file with us?

This file is located under <confluence-install>/conf path. Please, be careful to not share any sensitive information with this screenshot, such as instance URL.

Also, could you clarify if you restarted Confluence after applying the workaround to your instance?