Re: [us...@httpd] Virtual hosts + proxy

2009-03-30 Thread Ignacio Avellino
> You router only sees the IP address and the port, and so can only make > decisions based on that. The router doesn't see the URL unless it's an > application level router, which I asume it isn't or you wouldn't be > asking this here. Krist: You're right .. it's a plain old router, not applicat

Re: [us...@httpd] Virtual hosts + proxy

2009-03-29 Thread Krist van Besien
On Fri, Mar 27, 2009 at 10:05 PM, Ignacio Avellino wrote: > The main problem is that our router/firewall sends all requests on port 80 > to one server only (192.168.100.5), despite a subdomain specified in the > URL. You router only sees the IP address and the port, and so can only make decision

Re: [us...@httpd] Virtual hosts + proxy

2009-03-27 Thread Ignacio Avellino
> My first suggestion is comment out the proxy stuff for now, and just > see if you can get vhosts working in general. You can test this by > giving the vhosts a different DocumentRoot from the main server, and > you'll know it's working based on what DocumentRoot is being served. VHost is running

Re: [us...@httpd] Virtual hosts + proxy

2009-03-27 Thread Ignacio Avellino
> Your namevirtualhost *:80 line should match what you have in your > Thanks > You'll also want a Listen 80 line somewhere. It is already listenting on the default port (80), so I didn't add the line. > Some other things that I notice. The first argument you have on ProxyPass > looks a lot li

Re: [us...@httpd] Virtual hosts + proxy

2009-03-27 Thread Brian Mearns
On Fri, Mar 27, 2009 at 3:09 PM, Ignacio Avellino wrote: > Biran! > Thanks a million for the response > >> Think you need: >> >> NameVirtualHost * > > I have: > NameVirtualHost *:80 > on httpd.conf > > If I change it to > NameVirtualHost * > > when I start httpd I get: > > Starting httpd: [Fri Mar

Re: [us...@httpd] Virtual hosts + proxy

2009-03-27 Thread chris
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > If I change the directive from to en > every VirtualHost, I get the same error ... > And the page is still not working > > What do you suggest? > Just in case it helps, what I'm trying to do is to expose 4 web pages, and > one is on a different p

Re: [us...@httpd] Virtual hosts + proxy

2009-03-27 Thread Ignacio Avellino
Biran! Thanks a million for the response > Think you need: > > NameVirtualHost * I have: NameVirtualHost *:80 on httpd.conf If I change it to NameVirtualHost * when I start httpd I get: Starting httpd: [Fri Mar 27 16:01:40 2009] [error] VirtualHost *:80 -- mixing * ports and non-* ports with

Re: [us...@httpd] Virtual hosts + proxy

2009-03-27 Thread Brian Mearns
On Fri, Mar 27, 2009 at 2:08 PM, Ignacio Avellino wrote: > Hello apachers! > I have a question, that I have researched extensively on the web, without > getting to work what I want. > Basically, we have different web pages on different hosts on my > Institution. > Since we have only one public IP,

[us...@httpd] Virtual hosts + proxy

2009-03-27 Thread Ignacio Avellino
Hello apachers! I have a question, that I have researched extensively on the web, without getting to work what I want. Basically, we have different web pages on different hosts on my Institution. Since we have only one public IP, all the requests that get on port 80 are forwarded to our main server