Hi jesus2099, as you often link to tickets: could you start using https links for that? It (mostly) works now, and would save me the copy target link→paste into address bar→insert „s“ dance?
Oh, and hurray for tracksets! 
Why, can’t you access the HTTP version anymore? You should consider installing an extension such as HTTPS Everywhere.
As long as the dashboard doesn’t work properly with HTTPS, HTTP is still the preferred schema for JIRA URLs.
2 Likes
I can, but it leaks state. IIRC, the Jira session cookie is also not „secure“, so going to the http version will expose your session.
I have, but am apparently too dumb to configure it…
What doesn’t work for you? The only problems I had is spurious redirects to http. This is bad, but doesn’t make the site less usable than going to http in the first place.
Yeah, I see (I don’t use the dashboard). Looks JIRA is still embedding lots of http links in the dashboard, which makes the mixed-content detection sad.
Hopefully once we update this will be solved: the update ETA is “shortly after moving to the new host” so in a few months I’d imagine.
2 Likes
Our company uses confluence not jira but the same setting needs to be changed.
You may need to edit the tomcat configuration.
You will Zlso need to set the base URL parameter in confluence to be a HTTPS URL.
https://confluence.atlassian.com/adminjiraserver071/integrating-jira-with-apache-using-ssl-802593043.html
That might be true, but I doubt it is worth worrying about until Jira is updated - that version is ancient 
HTTPS is much easier to configure with the later versions!
Pff, only in Internet time. It’s just a tool.
Do you replace your hammers, knifes, kitchen sink, and car every year because a new-and-enhanced model appears?
That said, if https support is wanted (which I hope), and better/easier in the newer versions, go for the upgrade. I’ll wait.
1 Like