Tomcat 7 0 43 INFO Error parsing HTTP request header

Question

I use Tomcat 7 0 43 with a websocket application  My app works fine in Tomcat 7 0 42 but with 43 I get the following output when I try to access my server on websockets   Sep 16  2013 3 08 34 AM org apache coyote http11 AbstractHttp11Processor process INFO  Error parsing HTTP request header  Note  further occurrences of HTTP header parsing errors will be logged at DEBUG level    My browser console shows the following    WebSocket connection to  ws   www testapp com socket notification 848df2e62fcf93e1b3 X-Atmosphere-tracking-i   Date 0 amp Content-Type application json  20charset UTF-8 amp X-atmo-protocol true  failed  Unrecognized frame opcode  5    Here is the access log for that request     GET  socket notification 848df2e62fcf93e1b3 X-Atmosphere-tracking-id 0 amp X-Atmosphere-Framework 2 0 2-javascript amp X-Atmosphere-Transport websocket amp X-Atmosphere-TrackMessageSize true amp X-Cache-Date 0 amp Content-Type application json  20charset UTF-8 amp X-atmo-protocol true HTTP 1 1    What has changed in Tomcat 7 0 43  What do I have to change

User · Answer

I had a similar issue  I was sending a POST request  using RESTClient plugin for Firefox  with data in the request body and was receiving the same message   In my case this happened because I was trying to use HTTPS protocol in a local tomcat instance where HTTPS was not configured

User · Answer

If you don t want to upgrade your tomcat  Add this line in your catalina properties  tomcat util http parser HttpParser requestTargetAllow       It works for me http   www zhoulujun cn zhoulujun html java tomcat 2018 0508 8109 html

User · Answer

In our case it turned out that the error happened because we have a custom filter in our application which does HttpServletResponse sendRedirect   to other url   For some reason  the redirection is not closing the keep-alive status of the connection  hence the timeout exception   We checked with Tomcat Docs and when we disabled the maxKeepAliveRequests by setting it s value to 1 and the error stopped showing up   For now we do not have the actual solution to the error

User · Answer

I had this issue when working on a Java Project in Debian 10 with Tomcat as the application server  The issue was that the application already had https defined as it s default protocol while I was using http to call the application in the browser  So when I try running the application I get this error in my log file  org apache coyote http11 AbstractHttp11Processor process INFO  Error parsing HTTP request header  Note  further occurrences of HTTP header parsing errors will be logged at DEBUG level   I however tried using the https protocol in the browser but it didn t connect throwing the error  Here s how I solved it  You need a certificate to setup the https protocol for the application  I first had to create a keystore file for the application  more like a self-signed certificate for the https protocol  sudo keytool -genkey -keyalg RSA -alias tomcat -keystore  usr share tomcat keystore  Note  You need to have Java installed on the server to be able to do this  Java can be installed using sudo apt install default-jdk  Next  I added a https Tomcat server connector for the application in the Tomcat server configuration file   opt tomcat conf server xml   sudo nano  opt tomcat conf server xml  Add the following to the configuration of the application  Notice that the keystore file location and password are specified  Also a port for the https protocol is defined  which is different from the port for the http protocol   lt Connector protocol  quot org apache coyote http11 Http11Protocol quot             port  quot 8443 quot  maxThreads  quot 200 quot  scheme  quot https quot             secure  quot true quot  SSLEnabled  quot true quot             keystoreFile  quot  usr share tomcat keystore quot             keystorePass  quot my-password quot             clientAuth  quot false quot  sslProtocol  quot TLS quot             URIEncoding  quot UTF-8 quot             compression  quot force quot             compressableMimeType  quot text html text xml text plain text javascript text css quot   gt   So the full server configuration for the application looked liked this in the Tomcat server configuration file   opt tomcat conf server xml    lt Service name  quot my-application quot  gt     lt Connector protocol  quot org apache coyote http11 Http11Protocol quot               port  quot 8443 quot  maxThreads  quot 200 quot  scheme  quot https quot               secure  quot true quot  SSLEnabled  quot true quot               keystoreFile  quot  usr share tomcat keystore quot               keystorePass  quot my-password quot               clientAuth  quot false quot  sslProtocol  quot TLS quot               URIEncoding  quot UTF-8 quot               compression  quot force quot               compressableMimeType  quot text html text xml text plain text javascript text css quot   gt      lt Connector port  quot 8009 quot  protocol  quot HTTP 1 1 quot               connectionTimeout  quot 20000 quot               redirectPort  quot 8443 quot    gt      lt Engine name  quot my-application quot  defaultHost  quot localhost quot  gt        lt Realm className  quot org apache catalina realm LockOutRealm quot  gt           lt Realm className  quot org apache catalina realm UserDatabaseRealm quot               resourceName  quot UserDatabase quot   gt       lt  Realm gt        lt Host name  quot localhost quot   appBase  quot webapps quot            unpackWARs  quot true quot  autoDeploy  quot true quot  gt            lt Valve className  quot org apache catalina valves AccessLogValve quot  directory  quot logs quot               prefix  quot localhost access log quot  suffix  quot  txt quot               pattern  quot  h  l  u  t  amp quot  r amp quot   s  b quot    gt        lt  Host gt     lt  Engine gt   lt  Service gt   This time when I tried accessing the application from the browser using  https   my-server-ip-address https-port  In my case it was  https 35 123 45 6 8443  it worked fine  Although  I had to accept a warning which added a security exception for the website since the certificate used is a self-signed one  That s all  I hope this helps

User · Answer

Check  if you are not accidentally requesting HTTPS protocol instead of HTTP   I have overlooked that I was requesting https   localhost     instead of http   localhost     and it resulted to this weird message

User · Answer

If there are too many cookies cached  it breaks the server  the size of a request header is too big     Clearing the cookies can fix this issue as well

User · Answer

If you have this listener        lt Listener className  org apache catalina core AprLifecycleListener  SSLEngine  on   gt    on your server xml  remove it and try  You can not use a keystore if you are using the APR connector

User · Answer

I tried all of the above  nothing worked for me  Then I changed tomcat port numbers both HTTP 1 1 and Tomcat admin port and it got solved   I see other solutions above worked for the people but it is worth to try this one if any of the above doesn t work   Thanks everyone

User · Answer

For me  the problem was passing in a larger than normally expected HTTP header  I resolved it by setting maxHttpHeaderSize  1048576  attribute on the Connector node in server xml

User · Answer

My problem occurs when I try to open https  I don t use SSL   It s Tomcat bug   Today 12 02 2017 newest official version from Debian repositories is Tomcat 8 0 14  Solution is to download from official site and install newest package of Tomcat 8  8 5  9 or upgrade to newest version 8 5 x  from jessie-backports    Debian 8  Add to  etc apt sources list  deb http   ftp debian org debian jessie-backports main   Then update and install Tomcat from jessie-backports  sudo apt-get update  amp  amp  sudo apt-get -t jessie-backports install tomcat8

[java] Tomcat 7.0.43 "INFO: Error parsing HTTP request header"

Examples related to java

Examples related to tomcat

Examples related to servlets

Examples related to tomcat7