Type Exception Report
Message Invalid character found in the request target [/router.html?a=/mtjj/337762.shtmltitle=0xe30x800x8a0xe40xb80xad0xe50x9b0xbd0xe50x860xb60xe90x870x910xe60x8a0xa50xe30x800x8b0xef0xbc0x9a0xe60x9d0x8e0xe50x880xa90xe50x890x910xef0xbc0x9a0xe40xb80x8b0xe50x8d0x8a0xe50xb90xb40xe90x920xa20xe50xb80x820xe40xb80x8d0xe40xbc0x9a0xe50xb70xae0xe50xb80x820xe50x9c0xba0xe70x9b0x910xe70xae0xa10xe40xbb0x8d0xe90x9c0x800xe50x8a0xa00xe50xbc0xba& ]. 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 [/router.html?a=/mtjj/337762.shtmltitle=0xe30x800x8a0xe40xb80xad0xe50x9b0xbd0xe50x860xb60xe90x870x910xe60x8a0xa50xe30x800x8b0xef0xbc0x9a0xe60x9d0x8e0xe50x880xa90xe50x890x910xef0xbc0x9a0xe40xb80x8b0xe50x8d0x8a0xe50xb90xb40xe90x920xa20xe50xb80x820xe40xb80x8d0xe40xbc0x9a0xe50xb70xae0xe50xb80x820xe50x9c0xba0xe70x9b0x910xe70xae0xa10xe40xbb0x8d0xe90x9c0x800xe50x8a0xa00xe50xbc0xba& ]. 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.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1794) org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) 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:63) java.base/java.lang.Thread.run(Unknown Source)
Note The full stack trace of the root cause is available in the server logs.