Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Keep-Alive Header in JIRA/Confluence is Not Compliant

I have recently upgraded my JIRA/Confluence datacenter instances to version 8.20.3 and 7.4.14 respectively.

After upgrading, HTTP responses on both have included the keep-alive header, which you can see here (you can check out my public site here:

This header is technically not allowed in HTTP/2, as you can see here:

While most browsers ignore it, some versions of Safari (v13 and older) will not load the page if the header is present.  You can see that in action here:

Here are some additional points:

  • While both of these sites are being served via a reverse proxy, I have also connected directly to the host server to confirm it is coming from JIRA/Confluence directly.
  • If I block the Keep-Alive header via the reverse proxy, Confluence's synchrony breaks.
  • It doesn't seem to be just me, for instance, Apache's JIRA instance is sending the keep-alive header:

Is there any way of disabling the keep-alive header so that my site will work in Safari (and be HTTP compliant)?

1 answer

p.s. it seems like if I set the maxKeepAliveRequests option in my server.xml file to 1 it will stop the keep-alive header from being sent - but will that break anything?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events