Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC
来源:互联网 发布:美国交通事故数据集 编辑:程序博客网 时间:2024/06/06 01:43
前言:
公司一个在WinServer中运行的很稳定的Web项目迁移到Linux上。并且Web容器版本从tomcat-6.0.41升级到tomcat-7.0.81。迁移后进行测试,在点击某一个页面的时候出现了Http:400的错误。
Oct 26, 2017 2:15:30 AM org.apache.coyote.http11.AbstractHttp11Processor processINFO: Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.java.lang.IllegalArgumentException: Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC 3986at org.apache.coyote.http11.InternalInputBuffer.parseRequestLine(InternalInputBuffer.java:189)at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1028)at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:318)at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)at java.lang.Thread.run(Thread.java:745)
解决过程:
经过排查,是访问页面的url中含有字符“|”,导致这个问题。原因如下:
查询资料得知,tomcat-7.0.73, 8.0.39, 8.5.7 版本后增加了对请求的校验。
RFC3986文档规定,Url中只允许包含英文字母(a-zA-Z)、数字(0-9)、-_.~4个特殊字符以及所有保留字符。
RFC3986中指定了以下字符为保留字符:
!*'();:@&=+$,/?#[]
还有一些字符,当他们直接放在Url中的时候,可能会引起解析程序的歧义。这些字符被视为不安全字符,原因有很多。
->空格Url在传输的过程,或者用户在排版的过程,或者文本处理程序在处理Url的过程,都有可能引入无关紧要的空格,或者将那些有意义的空格给去掉->引号以及<>引号和尖括号通常用于在普通文本中起到分隔Url的作用->#通常用于表示书签或者锚点->%百分号本身用作对不安全字符进行编码时使用的特殊字符,因此本身需要编码->{}|\^[]`~某一些网关或者传输代理会篡改这些字符
故,该错误是由于请求中url参数“违法”造成的。
解决办法:
① 降低tomcat版本(本文未采用);
② 对tomcat的http请求进行特殊字符过滤:
配置tomcat的catalina.properties(路径:tomcat/config)
添加或者修改:
tomcat.util.http.parser.HttpParser.requestTargetAllow=|
当然还有另外一种方法,就是将所有的参数都进行编码
阅读全文
1 0
- Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC
- Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC
- invalid character found in the request target the valid characters are defined in rfc 7230 and rfc 3
- invalid character found in the request target the valid characters are defined in rfc 7230 and rfc
- Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC
- invalid character found in the request target the valid characters are defined in rfc 7230 and rfc 3
- Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC
- Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC
- 解决Invalid character found in the request target. The valid characters are defined in RFC 7230 and RF
- 解决Invalid character found in the request target. The valid characters are defined in RFC 7230 and RF
- 解决Invalid character found in the request target. The valid characters are defined in RFC 7230 and RF
- 解决Invalid character found in the request target. The valid characters are defined in RFC 7230 and RF
- 异常:Invalid character found in the request target. The valid characters are defined in RFC 3986
- 异常:Invalid character found in the request target. The valid characters are defined in RFC 3986
- 异常:Invalid character found in the request target. The valid characters are defined in RFC 3986
- 解决Tomcat报Invalid character found in the request target. The valid characters are defined in RFC 3986
- Tomcat 报 The valid characters are defined in RFC 7230 and RFC 3986
- The valid characters are defined in RFC 7230 and RFC 3986
- Linux查看系统资源占用
- noteBook2.15-C#基础第十五天
- 7、Python3 函数学习记录
- HBase数据导入工具总结
- MySQL百万级数据库查询优化技巧
- Invalid character found in the request target. The valid characters are defined in RFC 7230 and RFC
- 润乾报表 填报表组如何控制默认显示哪个sheet页
- dnsrecon 侦察
- Python为何物Swift更不懂
- Altium Designer中如何在PCB板图上绘制安装孔,孔的尺寸
- Java之学习笔记-------------查找算法
- ClassPathXmlApplicationContext 初始化流程
- 策略模式的基本运用
- Kotlin极简教程(第一章 Kotlin简介)