Closed
Bug 136661
Opened 22 years ago
Closed 22 years ago
Proxy: (manual) port==0 should make direct connection.
Categories
(Core :: Networking, defect)
Core
Networking
Tracking
()
VERIFIED
WORKSFORME
People
(Reporter: benc, Unassigned)
Details
(Keywords: testcase)
Drift from bug 54804: ------- Additional Comment #24 From Robert Hershberger 2001-11-10 02:57 ------- I have build 2001110803 loaded on a Win98 plateform (I know stop groaning and/or laughing), and have experienced one problem with proxy setup. I was using Netscape 4 previously and migrated a profile from there. All the proxy settings where correctly replicated, except http & socks, both of which had port settings of zero (0). Not a terrible problem for me, but a normal Joe might run into one. The effect of no port setting emulated a DNS request failure, the error was something to the effect of "Unable to resolve www.mozilla.org." And having seen this problem in the past I checked that my proxy server was running correctly first (I pointed Netscape at www.mozilla.org). Once I knew the proxy was working it was a short jump to finding the incorrect settings. Thanks for your time. RTH Contributor never opened bug or answered, so the migration aspects can't be addressed. However, we should test for port==0 and make sure general behavior is correct. The "error is confusing when using proxy" is bug 56629.
RESOLVED/WFM: mozilla 1.1, Mac OS X, Win 98
V/wfm. We probably should have made it simply error correctly when we had the chance.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•