公众号矩阵

换一换

极限施工 +关注

分享各种极限环境下的施工条件，带你看想不到的工程机械。

轮挖小帮手 +关注

让更多人认识到轮挖施工的便捷性，推荐值得信赖的轮挖品牌给用户。

砼相汇 +关注

“砼心” “砼行” “ 砼赢 ” ，为您提供全方位的智能化综合解决方案。

吊尔鋃鐺 +关注

关注起重机械，了解产品信息、保养知识，抢先知晓行业动态、市场信息。

机甲吹哨人 +关注

5G在工程机械领域的创新应用。5G在设备状态监控、远程维修、多设备协同作业、远程操控等领域的应用及创新。

HTTP Status 400 – Bad Request

Type Exception Report

Message Invalid character found in the request target [/include/news_detail_about_brand_2019.jsp?sortNum=,22,23,25,9,1,&brand=0xe90x990x860xe50xbe0xb70xe70xad0x910xe60x9c0xba&logo=&keyword=,9646,5fb7,7b51,673a-,6405,62cc,7ad9-,54c8,8428,514b,65af,5766&id=128516&productBrandId=0 ]. 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 [/include/news_detail_about_brand_2019.jsp?sortNum=,22,23,25,9,1,&brand=0xe90x990x860xe50xbe0xb70xe70xad0x910xe60x9c0xba&logo=&keyword=,9646,5fb7,7b51,673a-,6405,62cc,7ad9-,54c8,8428,514b,65af,5766&id=128516&productBrandId=0 ]. The valid characters are defined in RFC 7230 and RFC 3986
	org.apache.coyote.http11.Http11InputBuffer.parseRequestLine(Http11InputBuffer.java:494)
	org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:271)
	org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
	org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
	org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
	org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	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.lang.Thread.run(Thread.java:748)

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

Apache Tomcat/9.0.62