On Wed, May 16, 2012 at 8:50 PM, Matt Brennan <brennanma@...> wrote:
> This is how I do this. In my RT_SiteConfig.pm I have:
> 'https://' > . RT->Config->Get('WebDomain')
> All traffic on my RT instance is done via HTTPS. I also have an Apache
> rewrite rule in case someone navigates to HTTP instead (as users often do).
You don't need this. WebDomain, WebPort and WebPath is enough in most cases.
As documentation in versions says you set WebBaseURL or other options only
in very specific cases, for example when you want to server RT over HTTPS
from port 10000.
Topic starter needs CanonicalizeRedirectURLs option. He uses reverse proxy. By
default for redirects RT guesses a few bits from ENV variables (set by
This allows you to run the same RT instance with multiple entry points. However,
if you have something in front of RT then this guessing doesn't work.
> On Wed, May 16, 2012 at 11:20 AM, Giles Coochey <giles@...> wrote:
>> I have the following set up:
>> Clients --> Squid SSL Offload / Caching Reverse Proxy (HTTPS--->HTTP) -->
>> Apache Routing Proxy (HTTP) --> RT (HTTP)
>> RT (v4.0.5) itself is configured for HTTPS:
>> Set($WebDomain, 'www.domain.net');
>> Set($WebPath, '/ticket');
>> Set($WebPort, 443);
>> On going to Tools --> Configuration --> System Config I see that
>> WebBaseURL is correctly listed as https://www.domain.net >>
>> So if I navigate to https://www.domain.net/ticket/ >>
>> and Login then next page reverts to http...
>> What do you think I might be missing??
>> How can I force RT to HTTPS?