Received: (qmail 73357 invoked by uid 501); 19 Dec 2001 22:50:12 -0000 Message-Id: <20011219225012.73356.qmail@apache.org> Date: 19 Dec 2001 22:50:12 -0000 From: Aryeh Katz Reply-To: aryeh.katz@vasco.com To: submit@bugz.apache.org Subject: Listen and ProxyPass together don't work X-Send-Pr-Version: 3.110 >Number: 9201 >Category: mod_proxy >Synopsis: Listen and ProxyPass together don't work >Confidential: no >Severity: serious >Priority: medium >Responsible: apache >State: closed >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Wed Dec 19 15:00:01 PST 2001 >Closed-Date: Wed Dec 19 19:40:02 PST 2001 >Last-Modified: Thu Dec 20 08:20:00 PST 2001 >Originator: aryeh.katz@vasco.com >Release: 1.3.20 >Organization: >Environment: NT 4 SP 6 complied by : VC 6 sp3 :whatever ibm ships in websphere >Description: I'm not sure if this is a core issue or proxy issue. I assume it's proxy related. I was trying to test ProxyPass on a server that was configured to listen on 444. There were no other non-standard settings (LoadModule, etc.) In the server config, I added a ProxyPass, and ProxyPassReverse. I then tried to access the page on the regular port (80). The browser came back with "The Page cannot be displayed" A snoop of the wire traffic shows only tcpip syn and acq, no http data ever crosses the wire. >How-To-Repeat: Try placing the following lines at the end of the default httpd.conf Listen 444 ProxyPass / http://www.apache.org/ ProxyPassReverse / http://www.apache.org >Fix: >Release-Note: >Audit-Trail: From: "Aryeh Katz" To: submit@bugz.apache.org, apache-bugdb@apache.org, apbugs@apache.org Cc: Subject: Re: mod_proxy/9201: Listen and ProxyPass together don't work Date: Wed, 19 Dec 2001 18:02:59 -0500 one more note. mod_proxy wasn't compiled into the server, it was loaded using LoadModule. There was no ClearModuleList, nor was there an AddModule submit@bugz.apache.org wrote: > > Thank you very much for your problem report. > It has the internal identification `mod_proxy/9201'. > The individual assigned to look at your > report is: apache. > > >Category: mod_proxy > >Responsible: apache > >Synopsis: Listen and ProxyPass together don't work > >Arrival-Date: Wed Dec 19 15:00:01 PST 2001 -- Aryeh Katz VASCO www.vasco.com From: "Aryeh Katz" To: submit@bugz.apache.org, apache-bugdb@apache.org, apbugs@apache.org Cc: Subject: Re: mod_proxy/9201: Listen and ProxyPass together don't work Date: Wed, 19 Dec 2001 18:02:59 -0500 one more note. mod_proxy wasn't compiled into the server, it was loaded using LoadModule. There was no ClearModuleList, nor was there an AddModule submit@bugz.apache.org wrote: > > Thank you very much for your problem report. > It has the internal identification `mod_proxy/9201'. > The individual assigned to look at your > report is: apache. > > >Category: mod_proxy > >Responsible: apache > >Synopsis: Listen and ProxyPass together don't work > >Arrival-Date: Wed Dec 19 15:00:01 PST 2001 -- Aryeh Katz VASCO www.vasco.com 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. From: Marc Slemko To: Apache bugs database 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 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 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 >Unformatted: [In order for any reply to be added to the PR database, you need] [to include 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! ]