Solved: RE: [rt-users] Problem accessing RT located behind an apache proxy

Tue Oct 30 07:45:27 EDT 2007

Hi Andrew,

That option sounds like it should not be it as it works on the incoming headers but it does work.

I will work on adding this to the wiki. I do not think the Redhat/CentOS 5 server required this. The RedHat/Centos 4 server did though.

Thanks for the help!

Keith

-----Original Message-----
From: Andrew Smith [mailto:andrew at coolchilli.com]
Sent: Tue 10/30/2007 12:42 AM
To: Schincke, Keith D. (JSC-IT)[MEI]
Cc: Kris Boutilier; rt-users at lists.bestpractical.com
Subject: Re: [rt-users] Problem accessing RT located behind an apache proxy

Hi Keith,

Just a stab in the dark, have you tried ProxyPreserveHost On?  I know it 
rewrites the Host: value in the header, not sure if that would help RT.

Regards
Andrew

Schincke, Keith D. (JSC-IT)[MEI] wrote:
>
> Hey Kris,
>
> All of the html, images and javascript is loading correcting
>
> I used firebug to peak at the HTTP headers. It looks like the 
> "Location:" field is set to direct the browser to load the 
> Display.html file to display the updated ticket.
>
> The ProxyPass and ProxyPassReverse options should be changing the 
> response headers.
>
> Below is the relevant parts of my apache config file.
>
> Any help will be greatfully appricated.
>
> Keith
>
> RewriteEngine on
> RewriteLog /var/log/httpd/rewrite.log
> RewriteLogLevel 0
> RewriteRule ^/$ https://rt.example.com/rt/ [R,L]
> RewriteRule ^/rt$ https://10.0.0.1/rt/ [P,L]
> RewriteRule ^/rt/(.*)$ https://10.0.0.1/rt/$1 [P,L]
>
> ProxyRequests off
> SSLProxyEngine on
> <Location />
> ProxyPass https://10.0.0.1/
> ProxyPassReverse https://10.0.0.1/
> </Location>
>
>
>
> -----Original Message-----
> From: Kris Boutilier [mailto:Kris.Boutilier at scrd.bc.ca]
> Sent: Mon 10/29/2007 11:38 AM
> To: Schincke, Keith D. (JSC-IT)[MEI]
> Cc: rt-users at lists.bestpractical.com
> Subject: RE: [rt-users] Problem accessing RT located behind an apache 
> proxy
>
> Most likely you'll need to use something like mod_proxy_html to 
> manipulate occurances of the private address within the body of the 
> http stream. You could confirm this by using Wireshark to look at the 
> contents of the http replies on both sides of the Apache server and 
> see exactly where the offending addresses are being embedded.
>
> mod_proxy_html is a perfect tool for doing in-line rewrites of 
> javascript, css and other complexities generated by proxied web apps. 
> See http://apache.webthing.com/mod_proxy_html/
>
> Kris Boutilier
> Information Services Coordinator
> Sunshine Coast Regional District
>
> ________________________________
>
>         From: rt-users-bounces at lists.bestpractical.com 
> [mailto:rt-users-bounces at lists.bestpractical.com] On Behalf Of 
> Schincke, Keith D. (JSC-IT)[MEI]
>         Sent: Sunday, October 28, 2007 8:33 AM
>         To: rt-users at lists.bestpractical.com
>         Subject: [rt-users] Problem accessing RT located behind an 
> apache proxy
>        
>        
>
>
>         Hey Guys,
>        
>         I am having issues accessing parts of my RT installation while 
> it is located behind an apache proxy.
>        
>         My configuration is:
>           RT is installed on a server on a private network.
>           Apache is installed on a server on the public network that 
> will proxy with mod_rewrite access to the RT server.
>        
>         This configuration works great for most parts of the RT 
> system. Tickets can be looked at. Users can be added.
>         The problem occurs when a ticket or user is updated.
>        
>         When a ticket is updated, Update.html is called, the ticket is 
> update and the browser is redirected to Display.html.
>        
>         The redirect is what is causing my problems. The application 
> is tries to send the browser to the private IP address to load 
> Display.html.
>        
>         Here is my configuration:
>         Front end apache server:
>         Centos 4.5
>         httpd 2.0.52
>        
>         Here are the rewrite rules:
>         <VirtualHost *:80>
>            RewriteEngine on
>            RewriteLog /var/log/httpd/rewrite.log
>            RewriteLogLevel 2
>            RewriteRule ^/$ http://10.0.0.1/rt [P,L]
>            RewriteRule ^/(.*)$ http://10.0.0.1/$1 [P,L]
>            ProxyPass / http://rt.example.com/
>            ProxyPassReverse / http://rt.example.com/
>         </VirtualHost>
>        
>        
>         Backend server:
>         Debian etch
>         Aapche 2
>         RT 3.6
>        
>         My $WebBaseURL is http://rt.example.com
>        
>         Any suggestions on what may be causing the rewrite to not work 
> correctly?
>        
>         Thanks for any help,
>        
>         Keith
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> SAVE THOUSANDS OF DOLLARS ON RT SUPPORT:
>
> If you sign up for a new RT support contract before December 31, we'll take
> up to 20 percent off the price. This sale won't last long, so get in touch today. 
>     Email us at sales at bestpractical.com or call us at +1 617 812 0745.
>
>
> 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/20071030/48da05a7/attachment.htm>