[ale] Apache2 Proxy Question

[Wolf Halton]

Thanks Brian,
I thought it would end up being something simple.
I got it to work as a simple redirect with
Redirect 301 / http://servername.org:8080/redmine
and that looks pretty smooth.

It cuts off using the port 80 site directly, but solves the main problem,
which was getting access to redmine.

-Wolf

On Thu, Jan 19, 2012 at 10:37 AM, Brian Mathis <
brian.mathis+ale at betteradmin.com> wrote:

> This is not a problem with DNS, it's your apache config.  The URL in
> the ProxyPassReverse should be the URL that the web browser will be
> accessing; you have it set to the internal server.
>
> It should be something like this:
>
>    ProxyRequests     Off
>    ProxyPass /redmine http://127.0.0.1:8080/redmine
>     ProxyPassReverse /redmine http://your.web.site/redmine
>
>
> ❧ Brian Mathis
>
>
>
> On Wed, Jan 18, 2012 at 10:09 PM, Wolf Halton <wolf.halton at gmail.com>
> wrote:
> > I want to have a complicated web address
> http://sub.example.org:8080/redmine
> > be accessible at http://sub.example.org/redmine
> > This should be a simple redirect.
> > the following code is what I find at apache.org and is basically what I
> am
> > seeing everywhere.
> >
> > ProxyRequests     Off
> > ProxyPass /redmine http://127.0.0.1:8080/redmine
> > ProxyPassReverse /redmine http://127.0.0.1:8080/redmine
> >
> > What it gives me when I type http://sub.example.org/redmine in the
> address
> > bar of a browser is
> > http://sub.example.org/redmine/:8080/redmine
> > a broken nonexistent place.
> >
> > I tried the code above in the virtual server and in the mod_proxy
> > configuration and failed the same way with the code in either file.  At
> > least the failure is consistent.
> > /etc/apache2/sites-available/default
> > /etc/apache2/mods-available/proxy.conf
> >
> > I set the "A" record at the registrar (Network Solutions)  The base url
> > "example.org" points to a different ip address.
> > This server hostname = REDMINE-01 has 2 web servers running.  One is the
> > basic install apache2 listening at port 80, which I would like to be
> able to
> > keep if possible.
> > The other server is a Bitnami installed system listening at port 8080.
> >
> > 1.) should I set the other web server to listen at both ports and turn
> off
> > the apache2 server sitting on port 80?
> > 2.) could this be a cname issue that I could adjust at the registrar's
> dns
> > settings?
> > 3.) is it really a different problem and I have been trying to fix the
> wrong
> > problem for the last 11 hours?
> >
> > --
> > This Apt Has Super Cow Powers - http://sourcefreedom.com
> > Advancing Libraries Together - http://LYRASIS.org
> >
> >
> > _______________________________________________
> > Ale mailing list
> > Ale at ale.org
> > http://mail.ale.org/mailman/listinfo/ale
> > See JOBS, ANNOUNCE and SCHOOLS lists at
> > http://mail.ale.org/mailman/listinfo
> >
>
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>



-- 
This Apt Has Super Cow Powers - http://sourcefreedom.com
Advancing Libraries Together - http://LYRASIS.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20120119/337bd8e2/attachment.html