徐工环境1-2月销售收入再翻番
为持续推进公司规模快速发展，打造徐工“十三五”百亿环境产业板块，环境公司根据宏观形势及市场变化，在成套解决方案、细分市场突破、核心渠道建设方面投入更多资源精力，强力打造了更坚实的竞争力体系。目前，徐工环境成套化环卫机械逐步获得了更多的市场认可，并在全国各地树立了多个“标杆客户”。2017年徐工环境的目光更是放眼全球，全力实现环境产业纵向、横向全面拓展，信心满满、全速前进。（本文来自徐工 点击进入徐工网上购机页面）
徐工环境1-2月销售收入再翻番
2017-03-29
0
徐工环境公司继2016年实现销售收入同比增长160%后，今年1-2月继续高歌猛进实现销售收入同比增长122.66%，再次实现翻番，领跑全行业。
HTTP Status 400 – Bad Request
Type Exception Report
Message Invalid character found in the request target [/include/news_detail_about_brand.jsp?sortNum=,22,25,&brand=0xe50xbe0x900xe50xb70xa5&logo=/image/2015/02/20150204133009_715.jpg&keyword=0xe50xbe0x900xe50xb70xa50xe70x8e0xaf0xe50xa20x83,0xe90x940x800xe50x940xae0xe60x940xb60xe50x850xa5, ]. 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.jsp?sortNum=,22,25,&brand=0xe50xbe0x900xe50xb70xa5&logo=/image/2015/02/20150204133009_715.jpg&keyword=0xe50xbe0x900xe50xb70xa50xe70x8e0xaf0xe50xa20x83,0xe90x940x800xe50x940xae0xe60x940xb60xe50x850xa5, ]. 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.
