Categories
News

HTTP Status 400 – Bad Request


HTTP Status 400 – Bad Request


Kind Exception Report

Message Invalid character discovered within the request goal. The legitimate characters are outlined in RFC 7230 and RFC 3986

Description The server can not or is not going to course of the request attributable to one thing that’s perceived to be a shopper error (e.g., malformed request syntax, invalid request message framing, or misleading request routing).

Exception

java.lang.IllegalArgumentException: Invalid character discovered within the request goal. The legitimate characters are outlined in RFC 7230 and RFC 3986
	org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:483)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:682)
	org.apache.coyote.AbstractProcessorLight.course of(AbstractProcessorLight.java:66)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.course of(AbstractProtocol.java:810)
	org.apache.tomcat.util.internet.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1498)
	org.apache.tomcat.util.internet.SocketProcessorBase.run(SocketProcessorBase.java:49)
	java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	java.base/java.util.concurrent.ThreadPoolExecutor$Employee.run(ThreadPoolExecutor.java:635)
	org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	java.base/java.lang.Thread.run(Thread.java:840)

Notice The complete stack hint of the foundation trigger is on the market within the server logs.


Apache Tomcat/8.5.45



Source link

Leave a Reply

Your email address will not be published. Required fields are marked *