Good morning,

On 6/9/06 at 7:12 PM +0930, Michael Brader <[EMAIL PROTECTED]> wrote:

>Charlie Garrison writes:

> > Should I apply this patch to solve the problem, or is there some
> > other 'official' method to solve it?
>
>The official method which was pointed out after I sent in my patch is
>to use ProxyPassReverse as follows:
>
>    ProxyPass        / http://rtdb.bc.youramigo.com:8078/
>    ProxyPassReverse / http://rtdb.bc.youramigo.com:8078/
>
>See one of:
>
>http://httpd.apache.org/docs/1.3/mod/mod_proxy.html#proxypassreverse
>http://httpd.apache.org/docs/2.0/mod/mod_proxy.html#proxypassreverse
>http://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassreverse
>
>depending on your version of Apache. I don't know how to do
>ProxyPassReverse with mod_rewrite, so you might want to use my patch.

According the documentation, I should just be able to use ProxyPassReverse. OK,
I was going to say it didn't work but I just found my syntax error. That does
solve it.

It's not an ideal solution though since requests can come from different domain
names (eg. either .com.au or .com) but at least I know what I need to do now to
fix it. 

Thanks again for your help.


Charlie

-- 
   Charlie Garrison  <[EMAIL PROTECTED]>
   PO Box 141, Windsor, NSW 2756, Australia
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]


Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Reply via email to