Is it possible to provide http and https access to the same RT instance
without running completely separate configuration trees and mason
I have a setup now where the only difference between the http instance
and the https instance is that the former is defined within a
<VirtualHost *:80> container and the latter is within a container. Most things seem to work seamlessly; the only
exception (and it’s a doozy) I’ve found so far is the “create” button
from the “new ticket in ___ queue” screen. Is there a reason this button
needs to force a canonical URL instead of using a relative?
The reason I’d like to provide plaintext http is to avoid the SSL
performance hit for internal users, but I’d like external users to be
able to connect securely. Do I really need a duplicate setup to do that?
303-381-3802 (main support hotline)
303-381-3824 (my direct line)
. . .