Closed Bug 216329 Opened 22 years ago Closed 22 years ago

Firebird tries to load home page before finishing processing the auto proxy (PAC)

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 100022

People

(Reporter: wgianopoulos, Assigned: bugzilla)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030813 Mozilla Firebird/0.6.1+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5b) Gecko/20030813 Mozilla Firebird/0.6.1+ If you are behind a firewall requiring an automatic proxy configuration, and you either have your homepage set to something that requires proxying or if firebird is envoked specifying a URL that requires proxying it appears there is a race condition where the proxy pac processing might not be completed before the attempt is made to acces the page. If I set my homepage to http:/www.mozillazine.org/ it almost always fails on startup. Reproducible: Sometimes Steps to Reproduce: 1. install firebird on a PC behind a proxy 2. set the homepage to something that needs to conect via the proxy and will fail a dns lookup if it attempts to connect directly. 3. set up a rather long and complicated proxy pac file that will end up making access to the desired site go via the proxy and put this somewhere other than on the pc itself so that the pac must be laoded across the network 4. configure the connection settings in firebird to automatic proxy configuration url. 4. exit firebird 5. restart firebird Actual Results: recieved pop-up with error message www.mozillazine.org could not be found ... Expected Results: loaded the page via the proxy
*** This bug has been marked as a duplicate of 215457 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
How can this bug be a duplicate of BUG 215457? That bug report was against Mozilla and has already been fixed. This bug may in fact be the identical problem, but I am reporting it against Mozilla Firebird and the problem still exists in the latest nightly build. It's great that the problem has been resolved but the fix kind of needs to be put into Mozilla Firebird too!
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
yeah, the bug that was fixed (and that was also fixed for firebird... same source code actually!) is not this bug. duplicate resolution was invalid. this is however a duplicate of another bug, which isn't yet fixed. *** This bug has been marked as a duplicate of 100022 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.