Re: mod_proxy/9201: Listen and ProxyPass together don't work (fwd)

[Marc Slemko <ma...@znep.com>]

The following reply was made to PR mod_proxy/9201; it has been noted by GNATS.

From: Marc Slemko <ma...@znep.com>
To: Apache bugs database <ap...@apache.org>
Cc:  
Subject: Re: mod_proxy/9201: Listen and ProxyPass together don't work (fwd)
Date: Thu, 20 Dec 2001 08:18:13 -0800 (PST)

 ---------- Forwarded message ----------
 Date: Thu, 20 Dec 2001 09:35:04 -0500
 From: Aryeh Katz <ak...@vasco.com>
 To: marc@apache.org
 Subject: Re: mod_proxy/9201: Listen and ProxyPass together don't work
 
 here are the steps I did.
 1) set port to 80, which is in the default httpd.conf (or 82 on my
 second instance)
 2) set Listen to 443
 3) ran netstat -an, confirmed that there was nothing "old" listening on
 port 82 or 443
 4) started apache (as a service or from the command line)
 5) tried to connect to slash on port 82
 6) recieved browser error.
 7) when I run a netstat, I see that there is no listener on 80 (or 82)
 
 Why ? Isn't Listen in addition to Port?
 
 marc@apache.org wrote:
 > 
 > [In order for any reply to be added to the PR database, you need]
 > [to include <ap...@Apache.Org> in the Cc line and make sure the]
 > [subject line starts with the report component and number, with ]
 > [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 > ["Re: general/1098:").  If the subject doesn't match this       ]
 > [pattern, your message will be misfiled and ignored.  The       ]
 > ["apbugs" address is not added to the Cc line of messages from  ]
 > [the database automatically because of the potential for mail   ]
 > [loops.  If you do not include this Cc, your reply may be ig-   ]
 > [nored unless you are responding to an explicit request from a  ]
 > [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 > 
 > Synopsis: Listen and ProxyPass together don't work
 > 
 > State-Changed-From-To: open-closed
 > State-Changed-By: marc
 > State-Changed-When: Wed Dec 19 19:40:02 PST 2001
 > State-Changed-Why:
 > I don't see any bug here.  You tell your server to only listen on port 444, then try to connect on port 80.  You can't.  That is all working as it is supposed to.  If you want your server listening on port 80, you have to tell it to.
 
 -- 
 Aryeh Katz
 VASCO 			
 www.vasco.com