Modern HTTP Protocols Health Check Warning on Windows Server

[Paul Boyer]

My Jira Server instance is reporting a health check warning that modern HTTP protocols are not being used. Specifically, the warning reads:

Your content is served using outdated HTTP protocols. We recommend serving pages using HTTP/2 or newer to improve performance for users. Your navigation protocol is HTTP/1.1 and the resource protocol is unknown.

What steps need to be taken to rectify this issue for Jira v8.13.7 hosted on a Windows Server 2016 VM? Thanks!

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

This warning most often happens when you are using a very old version of Jira, or a misconfigured proxy in front of it.  Jira 8.13 won't do outdated protocols without a lot of configuration to downgrade it, so it is almost certainly your proxy, or possibly http services on the server you are running it on.

Could you explain more about the network setup?  What is the proxy and how is it configured?

[Paul Boyer]

Hello, and thanks for the reply.

It is interesting that I am seeing this issue on my Jira dev server (which is a clone of the production server, but with some machine specific configurations like SSL certs), but not the production server. 

Neither server is using a proxy. They are both using the default connector configured in the Server.xml file:

<Connector port="80" useBodyEncodingForURI="true" relaxedQueryChars="[]|{}^\`"<>" relaxedPathChars="[]|" redirectPort="443" protocol="HTTP/1.1" minSpareThreads="25" maxThreads="150" maxHttpHeaderSize="8192" enableLookups="false" disableUploadTimeout="true" connectionTimeout="20000" bindOnInit="false" acceptCount="100"/>

As for the underlying Window Server 2016 OS, I haven't made any customizations that didn't already exist on the production server. Anything specific that I need to check on at the OS level?