[SOLVED] Debian Apache2 Redirect or ProxyPass fails

saphil · 01-18-2012, 03:46 PM

Redmine is in its Bitnami world and running on its own webserver
at http://sub.example.org:8080/redmine
apache2 is running and presents a web site of its own at http://sub.example.org
example.org points to an entirely different machine.
These DNS "A" records are split out at the domain registrar.

Code:

     <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all
                # Point / to redmine
                # ----------------------------------------------------------
                #Alias /redmine/ :8080/redmine/
                #RedirectMatch 301 ^/redmine/$ :8080/redmine/
                #ProxyPass /redmine :8080/redmine
                #ProxyPassReverse /redmine :8080/redmine
                #these inside a container failed entirely
        </Directory>

        # Point / to redmine
                # ----------------------------------------------------------
        #Alias / :8080/redmine/ # Fails because the actual baseurl
                                #  is on a different box
        #RedirectMatch 301 ^/$ :8080/redmine/
        #ProxyPass http://HOSTNAME-01/redmine http://HOSTNAME-01:8080/redmine
        #ProxyPassReverse http://HOSTNAME-01/redmine http://HOSTNAME-01:8080/redmine
        #  RedirectMatch and ProxyPass both gave me a proxy to 
        #  http://sub.example.org/redmine/:8080/redmine/ 
        #  which is broken

Is there a better way to get a redirect to send sub.example.org/redmine to sub.example.org:8080/redmine? I might have to turn off the port 80 webserver entirely, then it would be an issue of putting an alias into the yaml file for redmine.

bathory · 01-18-2012, 04:30 PM

Hi,

You can use the following configuration (reverse proxy):

Code:

ProxyRequests     Off
ProxyPass /redmine http://127.0.0.1:8080/redmine
ProxyPassReverse /redmine http://127.0.0.1:8080/redmine

Regards

saphil · 01-18-2012, 08:49 PM

Quote:

Originally Posted by bathory

Hi,

You can use the following configuration (reverse proxy):

Code:

ProxyRequests     Off
ProxyPass /redmine http://127.0.0.1:8080/redmine
ProxyPassReverse /redmine http://127.0.0.1:8080/redmine

Regards

This sends me to http://sub.example.org/redmine/:8080/redmine
when I type http://sub.example.org/redmine in the address bar.
I am putting this in the /etc/apache2/sites-available/default file
should I be putting it in the mod_proxy.conf file instead?
/etc/apache2/mods-available/proxy.conf

saphil · 01-18-2012, 08:55 PM

Nope, when it is in the mod_proxy it fails exactly the same way.

bathory · 01-19-2012, 12:22 AM

Hi,

Quote:

This sends me to http://sub.example.org/redmine/:8080/redmine
when I type http://sub.example.org/redmine in the address bar.

Are you sure it's not your browser cache? I guess you're restarting apache after making changes.

Quote:

I am putting this in the /etc/apache2/sites-available/default file
should I be putting it in the mod_proxy.conf file instead?

I'm not familiar with debian's apache config files, but I guess you need to put those directives in the sub.example.org vhost config (something like /etc/apache2/sites-enabled/<sub-example>), unless it's your default vhost.
Also try to put those directives outside of the <Directory ...></Directory> part.

Regards

saphil · 01-19-2012, 08:37 AM

I went a different route, in the end.
I had discovered the ProxyPass directives failed inside a container
The end solution was
inside the vhost file but outside of a location container:

Code:

Redirect 301 / http://sub.example.org:8080/redmine

Thanks for your help