HTTP Status 400 – Bad Request when URL Contains Special Characters
(Doc ID 3002485.1)
Last updated on FEBRUARY 05, 2024
Applies to:
Oracle REST Data Services - Version 17.4 and laterInformation in this document applies to any platform.
Symptoms
When using ORDS in Tomcat server and has a special characters in the URL ,getting 400 error
"Type Exception Report
Message Invalid character found in the request target [/ords/xxx/xxx.Save?p_list=20&p_employees=[object%20HTMLSelectElement]&p_deletions=[object%20HTMLSelectElement] ]. 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 [/ords/wbs/HR051.Save?p_list=20&p_employees=[object%20HTMLSelectElement]&p_deletions=[object%20HTMLSelectElement] ]. 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:834)
Note The full stack trace of the root cause is available in the server logs."
Message Invalid character found in the request target [/ords/xxx/xxx.Save?p_list=20&p_employees=[object%20HTMLSelectElement]&p_deletions=[object%20HTMLSelectElement] ]. 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 [/ords/wbs/HR051.Save?p_list=20&p_employees=[object%20HTMLSelectElement]&p_deletions=[object%20HTMLSelectElement] ]. 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:834)
Note The full stack trace of the root cause is available in the server logs."
Changes
ORDS Deployed in Tomcat Server
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |