Changes to running over HTTPS

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




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

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. 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 Join to answer
Community showcase
Maarten Cautreels
Posted Thursday in Off-topic

Friday Fun: What's your favourite beer/drink

As a Belgian, beer-lover and home brewer, beer is one of my great passions. I love the fact that with just a few ingredients (usually just water, hop and malt) you can create so many different tastes...

311 views 38 10
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot