HTTP Status 400 – Bad Request

您所在的位置:网站首页 律师书面意见书 HTTP Status 400 – Bad Request

HTTP Status 400 – Bad Request

2024-07-13 13:17| 来源: 网络整理| 查看: 265

HTTP Status 400 – Bad Request

Type Exception Report

Message Invalid character found in the request target [/uploadFiles/crawler_t_src_bond_doc/20190xe50xb90xb40xe50xb90xbf0xe40xb80x9c0xe70x9c0x810xef0xbc0x880xe60x9c0xac0xe70xba0xa70xef0xbc0x890xe70x8f0xa00xe60xb10x9f0xe40xb80x890xe80xa70x920xe60xb40xb20xe60xb00xb40xe80xb50x840xe60xba0x900xe90x850x8d0xe70xbd0xae0xe50xb70xa50xe70xa80x8b0xe40xb80x930xe90xa10xb90xe50x800xba0xe50x880xb80xef0xbc0x880xe40xb80x800xe60x9c0x9f0xef0xbc0x89--20190xe50xb90xb40xe50xb90xbf0xe40xb80x9c0xe70x9c0x810xe60x940xbf0xe50xba0x9c0xe40xb80x930xe90xa10xb90xe50x800xba0xe50x880xb80xef0xbc0x880xe40xb80x800xe60x9c0x9f0xef0xbc0x890xe60xb30x950xe50xbe0x8b0xe60x840x8f0xe80xa70x810xe40xb90xa6.pdf]. 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 [/uploadFiles/crawler_t_src_bond_doc/20190xe50xb90xb40xe50xb90xbf0xe40xb80x9c0xe70x9c0x810xef0xbc0x880xe60x9c0xac0xe70xba0xa70xef0xbc0x890xe70x8f0xa00xe60xb10x9f0xe40xb80x890xe80xa70x920xe60xb40xb20xe60xb00xb40xe80xb50x840xe60xba0x900xe90x850x8d0xe70xbd0xae0xe50xb70xa50xe70xa80x8b0xe40xb80x930xe90xa10xb90xe50x800xba0xe50x880xb80xef0xbc0x880xe40xb80x800xe60x9c0x9f0xef0xbc0x89--20190xe50xb90xb40xe50xb90xbf0xe40xb80x9c0xe70x9c0x810xe60x940xbf0xe50xba0x9c0xe40xb80x930xe90xa10xb90xe50x800xba0xe50x880xb80xef0xbc0x880xe40xb80x800xe60x9c0x9f0xef0xbc0x890xe60xb30x950xe50xbe0x8b0xe60x840x8f0xe80xa70x810xe40xb90xa6.pdf]. The valid characters are defined in RFC 7230 and RFC 3986 org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:512) org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:503) org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65) org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:818) org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1626) 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:748)

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

Apache Tomcat/8.5.59


【本文地址】


今日新闻


推荐新闻


CopyRight 2018-2019 办公设备维修网 版权所有 豫ICP备15022753号-3