Changes to running over HTTPS

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?

 

1 answer

1 accepted

This widget could not be displayed.

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. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Friday in Jira

New 5k User Limit and Other Cloud Updates

Hi all! Lauren here from the Enterprise Cloud marketing team.  I have some exciting Cloud updates from #AtlassianSummit that I wanted to share. We want everyone in your organization to be ab...

88 views 0 2
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you