RT2/3 with HTTP and HTTPS

Hi.

I am wondering if it is possible to use RT (2 or 3) in the following setting:

-HTTP with NameVirtualHost: http://support.company.com/
-HTTPS with (real) virtual host: https://secure.company.com/support/

Reason:
Normal (HTTP) sites are hosted on one IP address. As this is not possible for
HTTPS, you have to use either one IP address per site or use a dedicated
HTTPS host (like secure.company.com).

TIA.

Best regards,
Matthias

“MJ” == Matthias Juchem lists@konfido.de writes:

MJ> Normal (HTTP) sites are hosted on one IP address. As this is not
MJ> possible for HTTPS, you have to use either one IP address per site
MJ> or use a dedicated HTTPS host (like secure.company.com).

You can also run https on alternate port numbers like

https://foo.example.com:4999/

if you want. That’s what I do. My RT instances run on private high
number ports under SSL with self-signed certs. All I want to do is
prevent packet eavesdropping when I’m out in public networks, and this
suffices. I don’t run RT without SSL.

MJ> Normal (HTTP) sites are hosted on one IP address. As this is not
MJ> possible for HTTPS, you have to use either one IP address per site
MJ> or use a dedicated HTTPS host (like secure.company.com).

You can also run https on alternate port numbers like

https://foo.example.com:4999/

if you want. That’s what I do. My RT instances run on private high
number ports under SSL with self-signed certs. All I want to do is
prevent packet eavesdropping when I’m out in public networks, and this
suffices. I don’t run RT without SSL.

Sure.

Maybe my last e-mail was not clear enough. My problem is whether I can use 2
different URLs for the same RT instance.

For example:
http://support.company.com/
https://secure.company.com/support/

The last part of the URL can be the same, but the hostname is different
(because you can’t use NameVirtualHosts with HTTPS).

Configuring Apache to do this is no problem. But I don’t know much about the
internals of RT. I’m refering to the configuration variables $WebPath,
$WebBaseURL

$WebPath is not a real problem, but as $WebBaseURL contains the hostname,
there might be problems if the Apache virtual server name is different from
the server name in $WebPath.

Regards,
Matthias

“MJ” == Matthias Juchem lists@konfido.de writes:

MJ> $WebPath is not a real problem, but as $WebBaseURL contains the
MJ> hostname, there might be problems if the Apache virtual server
MJ> name is different from the server name in $WebPath.

You may get mix of http and https reference links in your pages (for
images) which may cause some browsers to barf. Stick with one or the
other for best results. Of course there’s nothing like actually
trying it…

Matthias Juchem wrote:

Maybe my last e-mail was not clear enough. My problem is whether I can use 2
different URLs for the same RT instance.

For example:
http://support.company.com/
https://secure.company.com/support/

$WebPath is not a real problem, but as $WebBaseURL contains the hostname,
there might be problems if the Apache virtual server name is different from
the server name in $WebPath.

$WebBaseURL also contains the scheme. You’d probably need two
separate RT_SiteConfigs (which implies two RT “installations”,
though they can both happily talk to the same backend.)

You should also be aware that you won’t be able to do this using
mod_perl for both virtuals; you want to run one or both under
fastcgi (or use a separate Apache instance to serve each.)

Phil Homewood, Systems Janitor, http://www.SnapGear.com
pdh@snapgear.com Ph: +61 7 3435 2810 Fx: +61 7 3891 3630
SnapGear - Custom Embedded Solutions and Security Appliances