I have been trying to figure out why this vulnerability shows up even after the traffic is set to route to HTTPS.
We have an internal page at jira.domain.com and it does redirect to https with a certificate from GoDaddy.
It looks like the Qualys scan is still picking up this vulnerability.
I have read that the traffic between Apache and Tomcat is still not encrypted so is it possibly picking up on that?
I apologize if this is a newb question but I am not sure what I should be looking at if the traffic is already redirected http to https.
Go “behind the screen” to meet some of the Confluence Cloud team. In this video series, we tackle some of the hard-hitting questions you never knew you wanted the answer to! Meet some of the ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events