[rt-users] using HTTPS: RT complains about $WebPort

Alex Peters alex at peters.net
Tue Jun 10 20:14:44 EDT 2014

I don't think RT can be configured that way.

Consider setting up RT for port 443 only, and setting up the web server to
redirect requests on port 80 to identical locations on port 443.  This
should deliver the same end user experience with the benefit of "coaxing"
users to move over to port 443.
On 07/06/2014 10:54 am, "Florin Andrei" <florin at andrei.myip.org> wrote:

> After opening port 443 and enabling SSL in the web server, RT complains
> all the time about this:
> [warning]: The requested port (443) does NOT match the configured WebPort
> (80).  Perhaps you should Set($WebPort, 443); in RT_SiteConfig.pm,
> otherwise your internal links may be broken.
> Yes, $WebPort is set to 80 in RT_Config.pm, it's the default value. But
> right now I have both 80 and 443 open, and a mix of clients using both. Is
> there a way to tell RT that both ports are okay?
> --
> Florin Andrei
> http://florin.myip.org/
> --
> RT Training - Boston, September 9-10
> http://bestpractical.com/training
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20140611/328bd535/attachment.html>

More information about the rt-users mailing list