[rt-users] Apache SSL for RT 3.6.1

[Sujith Emmanuel]

Thank you for the reply, seems like the only thing missing is the
virtualhost for port 80. Since the old app was running on server root, we
had not specified any virtualhost for that. Lets see, if this helps by
putting it in a separate container.

Thanks again.

Thanks and Regards
Sujith Emmanuel

On 11/14/06, Vonnahme, Nathan <nathan.vonnahme at bannerhealth.com> wrote:
>
>  Sounds like you need to have at least three virtualHost sections, because
> you have 3 hosts:
>
> 1.  server.mydomain.com (port 80)  = your old app
> 2.  server.mydomain.com:8080  = redirects to RT
> 3.  https://server.mydomain.com  (port 443)   = RT
>
>
> So,
>
>
> <VirtualHost 10.41.16.118:80 >
>
>  ServerName server.mydomain.com
>
> ** your "other" app's stuff goes here
>
> </VirtualHost>
>
>
>
> <VirtualHost 10.41.16.118:8080 >
>
> ServerName  server.mydomain.com
>
> RedirectMatch permanent (/.*) <https://server.mydomain.com$1>
>
> *https://server.mydomain.com$1
>
> </VirtualHost>
>
>
>
> <VirtualHost 10.41.16.118:443>
> *
>
> ServerName server.mydomain.com
>
> ** SSL directives here
>
> ** RT stuff here
>
> </VirtualHost>
>
>
>
>  ------------------------------
> *From:* rt-users-bounces at lists.bestpractical.com [mailto:
> rt-users-bounces at lists.bestpractical.com] *On Behalf Of *Sujith Emmanuel
> *Sent:* Friday, November 10, 2006 3:55 AM
> *To:* RT-Users at lists.bestpractical.com
> *Subject:* Fwd: [rt-users] Apache SSL for RT 3.6.1
>
>
> 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
> >
> >
>
> --
> This message has been scanned for viruses and
> dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
> believed to be clean.
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20061114/17d4cb05/attachment.htm>