I would start with this page: http://httpd.apache.org/docs/2.2/mod/mod_proxy.html There are great examples there.
Determine the match that you want. Then set up the destination to the right ip and port. It sounds like you had a match but maybe the destination was not what you wanted. Work by modifying one setting at a time. Kevin On Sun, Nov 25, 2012 at 11:00 PM, Chris Arnold <carn...@electrichendrix.com>wrote: > On Nov 25, 2012, at 10:17 PM, Kevin Castellow <kev.castel...@gmail.com> > wrote: > > Yes. That is exactly what a proxy would do for you. > Turn on logging to know for sure. > > Ok, I disabled the last proxy pass entry to the all vhost and now I do not > get the webmail login. What I was trying to do with the proxy pass entry > was proxy all https://mail.domain.com traffic to the email server. The > commented out proxy pass looks like: > Proxypass / https://192.168.124.3/ > Proxypassreverse / https://192.168.124.3/ > > How do I go about proxying https://mail.domain.com traffic to the email > server? > > > On Sun, Nov 25, 2012 at 10:14 PM, Chris Arnold < > carn...@electrichendrix.com> wrote: > >> We have a problem and I am trying to either confirm or deny it being an >> apache config mistake. 2 servers, 1 is 192.168.123.3 and 1 is >> 192.168.124.3. On the 192.168.124.3 server we have email; on the >> 192.168.123.3 server we have web server. When I go to >> https://192.168.123.3 I am presented with the webmail login. This should >> not be as the email is on 192.168.124.3. The 192.168.123.3 server is doing >> proxy pass. Could apache be redirecting this traffic to 192.168.124.3 and >> keeping the 192.168.123.3 address in the address bar? >> >> Sent from my iPhone >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org >> For additional commands, e-mail: users-h...@httpd.apache.org >> >> >
