I notice this in our 3.8.10 instance of RT as well. Our redirection of all
traffic to https picks it up and you continue to browse on port 443.
Ruslan mentions that it is a config issue,
Searching the Wiki and RT_Config.pm, I found that
Is what you need to set to ensure your links are formed correctly.
I’ve tested, works as expected.
Mike.On Wed, May 4, 2011 at 5:06 PM, Stoned Elipot email@example.com:
On Wed, May 4, 2011 at 9:49 PM, Alex Vandiver firstname.lastname@example.org wrote:
On Wed, 2011-05-04 at 14:27 -0500, Dario Landazuri wrote:
We are running an RT instance under https only. I just noticed a small
issue - when you’re looking at a ticket, the links for a requestor’s
other tickets are non-https (http://…). On our system, that leads to
a 404. Other links in the ticket (creating links, last ticket
transaction, etc) all properly go to https://…
This does look to be a bug; I’ll bounce your mail into the
issues.bestpractical.com to track it.
Playing around with a 4.0.0 test clone of a 3.8.10 RT instance I noticed
the same thing, both for the requestor’s other tickets links and for
the related tickets links.
Then I noticed that the 3.8.10 instance also exhibits the same
behaviour, only it was
masqueraded by the web server doing HTTP to HTTPS redirection :-}
Northern Ontario School of Medicine
955 Oliver Road
Thunder Bay, ON P7B 5E1
Phone: (807) 766-7331