HTTP Status 400 – Bad Request

by 透視報導編輯


HTTP Status 400 – Bad Request


Type Exception Report

Message Invalid character found in the request target [/article/3900674/%E6%96%B0%E8%82%A1IPO%EF%BD%9CSHEIN%E6%88%96%E5%B0%87%E5%80%AB%E6%95%A6%E4%B8%8A%E5%B8%82%E8%A8%88%E5%8A%83%E6%8E%A8%E9%81%B2%E8%87%B3%E4%B8%8B%E5%8D%8A%E5%B9%B4%E3%80%80%E8%8B%B1%E5%95%86%E6%A5%AD%E5%A4%A7%E8%87%A3%E7%A4%BA%E6%84%8F%E6%94%AF%E6%8C%81SHEIN%E4%B8%8A%E5%B8%82?mtc\u003d20065 ]. 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 [/article/3900674/%E6%96%B0%E8%82%A1IPO%EF%BD%9CSHEIN%E6%88%96%E5%B0%87%E5%80%AB%E6%95%A6%E4%B8%8A%E5%B8%82%E8%A8%88%E5%8A%83%E6%8E%A8%E9%81%B2%E8%87%B3%E4%B8%8B%E5%8D%8A%E5%B9%B4%E3%80%80%E8%8B%B1%E5%95%86%E6%A5%AD%E5%A4%A7%E8%87%A3%E7%A4%BA%E6%84%8F%E6%94%AF%E6%8C%81SHEIN%E4%B8%8A%E5%B8%82?mtc\u003d20065 ]. 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:61)
	java.base/java.lang.Thread.run(Thread.java:833)

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


Apache Tomcat/9.0.83



Source link

You may also like

Leave a Comment