346081 - drag performance when "auto-detect proxy setting" is enabled

Status: RESOLVED DUPLICATE of bug 769764

(Core :: Networking, defect)

Description

[snleo]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.5) Gecko/20060719 Firefox/1.5.0.5

When "auto-detect proxy setting" is enabled the FF will stuck for long time before the page is actually loaded. Sometimes the browser doesn't response when it's loading a remote page. Local pages can be loaded fast.

The problem does not exist when using the manual proxy settings.

Reproducible: Always

Steps to Reproduce:
1. set the auto-detect proxy setting on
2. open tabs and browse large pages. repeat until the the stuck becomes very obvious
3. manually add proxy and repeat step two. no such problem found.

Actual Results:  
The browser stucks and sometimes stopped responding


Please let me know if it's a common issue and when it can be fixed. thanks.

Comment 1

[Jo Hermans]

"auto-detect proxy setting" is trying to connect load a WPAD file from http://wpad/wpad.dat (same as Automatic Proxy configuration URL). Please check if it the same as your manual setting. You can load the file directly from that url.

Or are you using a dns-name and port ? In that case, it's due to the extra processing that a WPAD file might impose. I suggest that you talk to your ISP or to your system administrator in that case.

If you don't have a WPAD file, then it might be due to the timeout while trying to look for it, after which Firefox will try to go directly to the URL, as if no proxy exists (it it's possible on your network). That might indeed be slower than accessing through a proxy, because you're not using the cache inside the proxy.

Comment 2

[Daniel Mota Leite]

if the proxy.pac have a isInNet() call, the browser locks up trying to resolve the  dns, taking longer if that dns doesnt resolve

this is because the browser locks waiting to see the proxy.pac result to know if it will use a proxy (or what proxy) or not

i had to work around this by adding all internal domains to the proxy.pac (boring, but works) and using regexp url checks for the situations where someone puts the IP directly (shExpMatch)

i would say that this is a dupe of208287