Changes to running over HTTPS

[Andrew Beaven]

There was a change to this article yesterday that changed the connector protocol from 

org.apache.coyote.http11.Http11Protocol

 to 

org.apache.coyote.http11.Http11NioProtocol

Is this change only applicable to new installations of Jira or should I update my existing connector to match?

I'm using this same code to run Confluence over HTTPS. Does this same change apply?

[Branno · Accepted solution]

That change was made to reflect the current defaults for JIRA's Tomcat configuration. The difference between the two connector protocols is how it manages incoming connections and CPU threads.

HTTP/1.1 uses a blocking connector by default, by specifically calling out org.apache.coyote.http11.Http11NioProtocol it will force Tomcat to use a non-blocking connector. https://techblog.bozho.net/tomcats-default-connectors/ is a great read to get a basic understanding of the difference.

If you have a current working Atlassian applications running over HTTPS I wouldn't worry about changing it immediately (although it would be a good idea to make a change when you have a maintenance window). If, however, you've had problems with 503/504 errors it would make sense to change your configuration.