HTTP Status 400 – Bad Reques
  1. HTTP Status 400 – Bad Request
  2. Type Exception Report
  3.  
  4. Message Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986
  5.  
  6. 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).
  7.  
  8. Exception
  9.  
  10. java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986
  11.         org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:467)
  12.         org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:294)
  13.         org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:66)
  14.         org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:834)
  15.         org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1415)
  16.         org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
  17.         java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
  18.         java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
  19.         org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
  20.         java.base/java.lang.Thread.run(Thread.java:834)
  21. Note The full stack trace of the root cause is available in the server logs.
  22.  
  23. Apache Tomcat/9.0.16 (Ubuntu)
Parsed in 0.005 seconds