HTTP Status 400 – Bad Request


Type Exception Report

Message Invalid character found in the request target [/spaces/createrssfeed.action?types=blogpost&spaces=knowledgebase&maxResults=15&title=[%D0%91%D0%B0%D0%B7%D0%B0+%D0%B7%D0%BD%D0%B0%D0%BD%D0%B8%D0%B9+%D0%B4%D0%BB%D1%8F+%D0%BF%D0%BE%D0%BB%D1%8C%D0%B7%D0%BE%D0%B2%D0%B0%D1%82%D0%B5%D0%BB%D0%B5%D0%B9+%D0%9D%D0%93%D0%A3]+%D0%9D%D0%BE%D0%B2%D0%BE%D1%81%D1%82%D1%8C+%D0%9A%D0%B0%D0%BD%D0%B0%D0%BB&publicFeed=true ]. 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 [/spaces/createrssfeed.action?types=blogpost&spaces=knowledgebase&maxResults=15&title=[%D0%91%D0%B0%D0%B7%D0%B0+%D0%B7%D0%BD%D0%B0%D0%BD%D0%B8%D0%B9+%D0%B4%D0%BB%D1%8F+%D0%BF%D0%BE%D0%BB%D1%8C%D0%B7%D0%BE%D0%B2%D0%B0%D1%82%D0%B5%D0%BB%D0%B5%D0%B9+%D0%9D%D0%93%D0%A3]+%D0%9D%D0%BE%D0%B2%D0%BE%D1%81%D1%82%D1%8C+%D0%9A%D0%B0%D0%BD%D0%B0%D0%BB&publicFeed=true ]. The valid characters are defined in RFC 7230 and RFC 3986
	org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:494)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:271)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1789)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
	org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	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.


Apache Tomcat/9.0.65