[rt-users] Getting Request Tracker to stick to HTTPS

[Giles Coochey]

On 16/05/2012 16:24, Paul Tomblin wrote:
> In RT_Config, it looks like you shouldn't even have to specify
> WebBaseURL - it appears to look to see if WebPort is 443 and changes
> it to https accordingly.
Yes, it is doing that automatically (I have not specified WebBaseURL).

But it reverts me to http after logging in via https
>
> On Wed, May 16, 2012 at 11:20 AM, Giles Coochey<giles at coochey.net>  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?
>>
>
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4928 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20120516/3a5988a6/attachment.bin>