Closed
Bug 288929
Opened 20 years ago
Closed 20 years ago
Unable to connect to Internet using the AutoDetect proxy settings
Categories
(Firefox :: Settings UI, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: kerwin.ramos, Assigned: bugs)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 I searched for bugs but can't seem to find the exact problem. I use to ISPs to connect to the internet, one that is direct connection and one is through a proxy server. Ideally when I set the option to Auto Detect, I can always browse the web pages whichever connection I use. However, if I set the browser to Auto-Detect Proxy settings, and I connect to the internet using the ISP that requires proxy to connect to the internet, Firefox still behaves like it is connecting directly to the internet instead of connecting to the proxy first before using that to connect to the internet. Note that this is not just an ordinary proxy for anonymous surfing. Instead, requests have to pass this proxy server before going to the internet. Reproducible: Always Steps to Reproduce: 1. You need a connection that uses a proxy server to connect to the internet. It means that if the proxy server is down, you cannot access the internet 2. Access the internet with the options Auto Detect Proxy settings 3. Actual Results: Cannot access internet, status bar actually shows "connecting to yahoo.com" immediately Expected Results: Should be able to access internet, status bar should show connecting to xxxx.xxxx.xxx(proxy server) before connecting to yahoo.com
| Reporter | ||
Comment 1•20 years ago
|
||
aren't anyone checking out this bug?
can you please provide precise steps to setup this autodetect option in firefox?
| Reporter | ||
Comment 3•20 years ago
|
||
ok, go to Tools - Options - General tab, Connection Settings, then check the Auto-Detect proxy settings for this network
Comment 4•20 years ago
|
||
Does your ISP support WPAD (Web Proxy Auto-Discovery)? Does this work in IE?
| Reporter | ||
Comment 5•20 years ago
|
||
I'm not sure WPAD since this ISP is for my office. It does work with IE though. My analysis is that IE uses the connection settings for each dial-up account so it does not encounter this connection problem. I think the fix for this is just to have firefox check the settings of the dial up account you are using and use that settings if you have the Auto-Detect setting option selected.
Comment 6•20 years ago
|
||
There's a bug on using per-dialup account settings elsewhere, but this as reported is probably INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
| Reporter | ||
Comment 7•20 years ago
|
||
i don't think this should be counted as invalid unless you have really been unable to recreate this problem. as I have said, all you need is an ISP connection that needs a proxy to connect to the internet. no proxy, no internet access kind of scenario. What I really mean is Auto-Detect proxy settings does NOT work at all if you use proxy to connect to the internet rather than a proxy that makes anonymous surfing.
This is reproducable for me as well. I have to restart Firefox when I'm switching locations -- work->home and vica versa (I'm laptop user and I usually suspend at one location and resume at another). In the office I do have proxy with usernam/password authentification and it gets auto-detected but only when I restart Firefox. Back at home I do not have any proxy. I guess that Firefox should remember the IP address that was used while auto-discovering proxy and if this address changes, do the auto-discovery again.
Comment 9•18 years ago
|
||
sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change
QA Contact: mconnor → preferences
You need to log in
before you can comment on or make changes to this bug.
Description
•