> > You just need this rule: > > > > REDIRECT net 40240 tcp 80 - 87.145.23.55 Thank you! This rule didn't worked for me because these two rules were applied before the REDIRECT: HTTP/ACCEPT net $FW HTTPS/ACCEPT net $FW I just moved both ACCEPT after the REDIRECT and it works well ! (I need these two rules to accept http/https connections coming from other ip)
> While Tom is technically correct, there is a better way. > > Tom's solution redirects *all* port 80 traffic to the higher port. If > you are doing name-based virtual hosting and want to have some sites > served by Apache on port 80 and others redirected to the apache being > run by the user on the higher port, then you need to do something else. > > In the main Apache (the one listening on port 80), you need a virtual > host defined like this: > > <VirtualHost *:80> > ServerName www.example.com > ServerAdmin [EMAIL PROTECTED] > > <IfModule mod_proxy.c> > ProxyPass / http://87.145.23.55:40240/ > ProxyPassReverse / http://87.145.23.55:40240/ > </IfModule> > </VirtualHost> > > Then you configure the other Apache, you configure it however you like. > This will allow you to have different users run different Apache > instances on high number ports and still have all of them be accessible > from the outside world over port 80. Roberto, it's funny because I'm going to setup a reverse proxy as you explained above on the 40240 port. Why ? because I need to run the reverse proxy with a non-root user (it's easier to administer the server). However thank you for your great suggestion. regards, -- Stéphane GULLY http://www.zeitoun.net ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Shorewall-users mailing list Shorewall-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shorewall-users
