Mozilla/Firefox is passing the wrong address in call to PR_Connect, instead of Proxy's address.



Download & File Handling
13 years ago
10 years ago


(Reporter: William L. Hartzell, Unassigned)


Firefox Tracking Flags

(Not tracked)





13 years ago
User-Agent:       Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.7.10) Gecko/20050726
Build Identifier: Mozilla/5.0 (OS/2; U; Warp 4.5; en-US; rv:1.7.10) Gecko/20050726

Mozilla/Firefox, and all Netscape versions back to 2.02, are not using the proxy
to make SSL connections.  They are also not using the proxy for DNS in context
to this bug with calling SSL.  Julien Pierre says that the wrong address is
being passed in the PR_Connect call.  This is like the SOCK bug that was fixed a
while ago, the one where SOCK server was not being called for SSL connections.

Reproducible: Always

Steps to Reproduce:
1.  Establish a three machine setup: a router, a proxy, & a client.
2.  Scenario 1: Proxy is dual homed so that the client is connected to router
only through proxy.  Ip forwarding is off.  Static IP is in use. 
Mozilla/Firefox is configured to use proxy for all connections.  Calls to the
SSL links within the above URL will fail.  Error code -5994.
3.  Scenario 2: All machines are connected by a hub.  Router has a DHCP server
and serves proxy and client.  Client has a firewall that allows connections only
to proxy.  Firewall is raised after client get DNS and IP info from router. 
Mozilla/Firefox is configured to used the proxy for all connections.  Attempts
to connect to SSL links within the above URL will fail.  Error code -5994.

Actual Results:  
No connection images within to the above URL.

Expected Results:  
Connection to the above URL with all images displayed.

I've tested this on Windows XP with Mozilla 1.7.11 and the latest Firefox.  I've
also tested this with Firefox on Suse 9.3.  When they are configured like my
OS/2 client box, they also fail.  I remember that I've always had to lower the
firewall or enable IP forwarding with Netscape 2.02, 4.02, 4.61 for OS/2.  So
this has beeen a long standing problem.  It also exist in last night's private
build of SeaMonkey.
I can't tell from this bug, are you using a SOCKS proxy or not?

Comment 2

13 years ago
No sock proxy being used.  Bug has been fixed in SeaMonkey trunk and probably elsewhere.  Thanks!

Comment 3

10 years ago
Resolving per comment #2.
Last Resolved: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.