297288 - Import of Automatic Proxy Detection fails to work

Status: RESOLVED DUPLICATE of bug 266413

(Firefox :: Migration, defect)

Description

[Kyle Gordon]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.7.5) Gecko/20041110 Firefox/1.0

Hi,

We use automatic proxy detection here, and it is the default setting for
Internet Explorer. When Firefox is launched for the first time, it offers the
ability to import our Internet Explorer settings. This it does, but it seems to
miss out the Automatic Proxy Detection option, and leaves it using a Direct
Connection to the Internet. When manually selecting Auto-detect Proxy Settings
for this Network, it all works as intended. 

Regards

Kyle

Reproducible: Always

Steps to Reproduce:
1. Obtain freshly imaged system, or a clean install
2. Double check Internet Explorer options and verify Automatic Proxy Detection
is enabled and working.
3. Install Firefox
4. Run Firefox, import settings from Internet Explorer
5. Firefox will timeout waiting for start page (we block all unauthorised
outbound connections with iptables)
6. Change settings to Auto-detect proxy configuration for this network.
7. Try again, page loads and access shows up in proxy (Squid) logs.

Comment 1

[zug_treno]

Duplicate of bug 266413 and bug 259298?

Comment 2

[Kyle Gordon]

Duplicate of bug 259298? Quite possibly. I'll double check network.proxy.type  
when I get into work after the weekend.  

Comment 3

[Frank Wein [:mcsmurf]]

Yeah i can confirm that this doesn't work. But actually i think it wouldn't make
soo much sense at the current stage to import this setting because
Firefox/Mozilla (Necko) doesn't support everything that IE supports with
automatic proxy detection. Necko only supports the wpad method (look for host
wpad in local domain and then get http://wpad.local.domain/wpad.dat), IE also
supports getting the PAC URL via DHCP (option wpad-curl code 252 with a normal
dhcpd)).

Comment 4

[:Gavin Sharp [email: [e-mail]]]

Marking duplicate of bug 266413 - please reopen if network.proxy.type being set incorrectly is not the problem.

*** This bug has been marked as a duplicate of 266413 ***