Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors
tomcat進行http request解析的時候報錯,并將錯誤返回給客戶端了,具體的錯誤如下:org.apache.coyote.http11.AbstractHttp11Processor.processError parsing HTTP request headerNote:further occurrences of HTTP header parsing errors will be logged at DEBUG level.
就會報iib.requestheadertoolarge.error即Request header is too large,在網上搜索時,有的是因為這個設置導致的400,解決方法就是修改Tomcat的server.xml,在<Connectorport="8080"protocol="HTTP/1.1"connectionTimeout="20000"redirectPort="8443" />的配置中增加maxHttpHeaderSize的配置。
?? <Connector port="8080" protocol="HTTP/1.1"
?????????????? connectionTimeout="20000"
?????????????? redirectPort="8443" maxHttpHeaderSize="8192" />
??? <!-- A "Connector" using the shared thread pool-->
??? <!--
??? <Connector executor="tomcatThreadPool"
?????????????? port="8080" protocol="HTTP/1.1"
?????????????? connectionTimeout="20000"
?????????????? redirectPort="8443" />
??? -->
??? <!-- Define a SSL/TLS HTTP/1.1 Connector on port 8443
???????? This connector uses the NIO implementation that requires the JSSE
???????? style configuration. When using the APR/native implementation, the
???????? OpenSSL style configuration is required as described in the APR/native
???????? documentation -->
?? ?
??? <Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
?????????????? maxThreads="150" SSLEnabled="true" scheme="https" secure="true"
?????????????? clientAuth="false" sslProtocol="TLS" keystoreFile="C:/Users/Administrator/.keystore" keystorePass="123456"/>
?? ?
總結
以上是生活随笔為你收集整理的Error parsing HTTP request header Note: further occurrences of HTTP header parsing errors的全部內容,希望文章能夠幫你解決所遇到的問題。
- 上一篇: PostgreSQL数据库、表空间、角色
- 下一篇: 使用jsonpath从kettle转换j