Fwd: [rt-users] Apache SSL for RT 3.6.1

[Sujith Emmanuel]

Actually RT was running over http for some months, recently we made it
public and hence we need to serve it over ssl. Initial port was 8080 as the
other application was running on apache root. Then we used the rewrite rule
to shift to 443 but it was not working, hence moved to another port 8446
which was working fine. So old users typing 8080 will be taken to port 8446
now. i wanted to make the port for RT 443 so that there need not be any
extra rules in firewall, which somehow seems messed up.

Sorry for the confusion.

Thanks and Regards
Sujith Emmanuel

On 11/10/06, Jon Daley < bestpractical at jon.limedaley.com> wrote:
>
>         You don't want anything else running on port 443?  That should be
> simple then.  You don't need any rewriting or forwarding at all.  Take out
> RT, and get apache to respond to some "hello world" text file on port 443.
> Once you get that working, then put RT back in.
>
> On Fri, 10 Nov 2006, Sujith Emmanuel wrote:
> > Hi,
> >
> >    When i did this, i was taken to another application running on apache
> > root.
> >    Here is the case, i have an application running on port 80 and RT
> > running on 8080. In the RT's virtual host, i tried to forward everything
> to
> > port 443 but the page is going to the other application on root. When i
> > tried to forward to some no standard port like 8446, it is working.
> >
> > How do i solve this problem? I want the application in root to run on
> http
> > and RT on ssl.
> >
> > Any ideas?
> >
> > Thanks and Regards
> > Sujith Emmanuel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20061110/ebff8cad/attachment.htm>