HTTP Status 400 – Bad Request

·

Message Invalid character found in the request target [/news/20282/0xd80xae0xd90x880xd80xaf0xd80xb10xd90x88-3-0xd80xb30xdb0x8c0xd90x840xd90x860xd80xaf0xd80xb1-0xda0x860xdb0x8c0xd90x860xdb0x8c-0xd80xaf0xd80xb1-0xd80xa80xd80xa70xd80xb20xd80xa70xd80xb1-0xd80xa70xdb0x8c0xd80xb10xd80xa70xd90x86-25-0xd90x870xd80xb20xd80xa70xd80xb1-0xd80xaf0xd90x840xd80xa70xd80xb1-0xd90x850xd80xb90xd80xa70xd90x850xd90x840xd90x87-0xd80xb40xd80xaf]. The valid characters are defined in RFC 7230 and RFC 3986

HTTP Status 400 – Bad Request


Exception

Type Exception Report

java.lang.IllegalArgumentException: Invalid character found in the request target [/news/20282/0xd80xae0xd90x880xd80xaf0xd80xb10xd90x88-3-0xd80xb30xdb0x8c0xd90x840xd90x860xd80xaf0xd80xb1-0xda0x860xdb0x8c0xd90x860xdb0x8c-0xd80xaf0xd80xb1-0xd80xa80xd80xa70xd80xb20xd80xa70xd80xb1-0xd80xa70xdb0x8c0xd80xb10xd80xa70xd90x86-25-0xd90x870xd80xb20xd80xa70xd80xb1-0xd80xaf0xd90x840xd80xa70xd80xb1-0xd90x850xd80xb90xd80xa70xd90x850xd90x840xd90x87-0xd80xb40xd80xaf]. The valid characters are defined in RFC 7230 and RFC 3986 org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:499) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:260) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:868) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1589) 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:750)

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).

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


Apache Tomcat/9.0.37



منبع

0 پاسخ به “HTTP Status 400 – Bad Request”