HTTPS Error parsing HTTP request header

Bryden Mitchell

I have modified my jira server.xml https connector to:

 

<Connector
port="8081"
relaxedPathChars="[]|"
relaxedQueryChars="[]|{}^&#x5c;&#x60;&quot;&lt;&gt;"
maxThreads="150"
minSpareThreads="25"
connectionTimeout="20000"
enableLookups="false"
maxHttpHeaderSize="8192"
protocol="HTTP/1.1"
useBodyEncodingForURI="true"
acceptCount="100"
disableUploadTimeout="true"
bindOnInit="false"
secure="true"
scheme="https"
keyAlias="jira"
keystoreFile="/opt/atlassian/jira/jira.jks"
keystorePass="XXXX"
keystoreType="JKS"
/>

 

There are no errors in the jira boot logs, however, when attempting to access https, I get the error:

 

INFO [http-nio-8081-exec-23] org.apache.coyote.http11.Http11Processor.service Error parsing HTTP request header

Note: further occurrences of HTTP header parsing errors will be logged at DEBUG level.

Andy Heinzer

Hi Bryden,

Sorry to hear about this problem.  However that specific protocol was only valid in Jira versions 7.2.x and before.  Starting with Jira, Atlassian started to bundle a newer version of Apache Tomcat (the webserver that Jira uses).  This newer version of Tomcat is unable to use that specific protocol.  There was a bug report about trying to use this protocol in the server.xml for Jira 7.3 and higher versions in JRASERVER-63734.

Are you by chance running Jira 7.3 or higher here?  If so I would recommend the same resolution listed in that bug ticket:

Resolution

Modify JIRA_INSTALL/conf/server.xml. Change the protocol on your HTTPS connector to: protocol="org.apache.coyote.http11.Http11NioProtocol"

• If you do not use the HTTP Connector but use the AJP Connector instead, use the AJP NIO protocol instead.
  • The AJP connector is: protocol="org.apache.coyote.ajp.AjpNioProtocol"

Refer to Upgrade notes for 7.3 for instructions. See Running JIRA applications over SSL.

See Running JIRA applications over SSL or HTTPS for full directions on running JIRA over SSL or HTTPS.

And if you're using an older version of Jira, please let me know which one.  You might still be able to follow these same steps to avoid this error.

Regards,

Andy