Type Exception Report
Message Invalid character found in the request target [/spaces/createrssfeed.action?types=page&spaces=MP1X0&maxResults=15&title=[Mutterpass+1.0.0]+Pages+Feed&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=page&spaces=MP1X0&maxResults=15&title=[Mutterpass+1.0.0]+Pages+Feed&publicFeed=true ]. The valid characters are defined in RFC 7230 and RFC 3986 org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:482) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:263) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:928) org.apache.tomcat.util.net.Nio2Endpoint$SocketProcessor.doRun(Nio2Endpoint.java:1732) org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) org.apache.tomcat.util.net.AbstractEndpoint.processSocket(AbstractEndpoint.java:1295) org.apache.tomcat.util.net.SecureNio2Channel$HandshakeReadCompletionHandler.completed(SecureNio2Channel.java:104) org.apache.tomcat.util.net.SecureNio2Channel$HandshakeReadCompletionHandler.completed(SecureNio2Channel.java:97) java.base/sun.nio.ch.Invoker.invokeUnchecked(Unknown Source) java.base/sun.nio.ch.Invoker$2.run(Unknown Source) java.base/sun.nio.ch.AsynchronousChannelGroupImpl$1.run(Unknown Source) 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.base/java.lang.Thread.run(Unknown Source)
Note The full stack trace of the root cause is available in the server logs.