Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Die Funktionalität dieser Website ist durch Wartungsarbeiten eingeschränkt, die Ihr Erlebnis verbessern sollen. Wenn ein Artikel Ihr Problem nicht löst und Sie eine Frage stellen möchten, können Sie unsere Gemeinschaft über @FirefoxSupport auf Twitter, /r/firefox oder Reddit fragen.

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Firefox 12 and proxy

  • 6 Antworten
  • 14 haben dieses Problem
  • 14 Aufrufe
  • Letzte Antwort von dja2112

more options

Firefox 12 installed on Windows XP SP3. Auto-detect proxy settings for this network are not working. Only way to make Firefox 12 go through the proxy is to manual configure. Have a IIS server setup with wpad.dat. When Firefox 12 is auto-detect, from IIS logs it does not even try to get wpad.dat. Turning on the IP6 config statement does not solve the problem either. Same computer, IE get wpad.dat no problem.

Firefox 12 installed on Windows XP SP3. Auto-detect proxy settings for this network are not working. Only way to make Firefox 12 go through the proxy is to manual configure. Have a IIS server setup with wpad.dat. When Firefox 12 is auto-detect, from IIS logs it does not even try to get wpad.dat. Turning on the IP6 config statement does not solve the problem either. Same computer, IE get wpad.dat no problem.

Alle Antworten (6)

more options

If you select Auto-detect proxy settings, check in about:config the network.proxy.type if it has the number 4 value .


thank you

more options

Have tried all different kinds of settings. When Firefox 12 is set to auto-detect, indeed the about:config network.proxy.type user set integer is 4. From IIS logs, not even making the request for wpad.dat.

more options

Firefox, is attempting to fetch the file from http://wpad/wpad.dat instead of http://wpad.your.domain.tld/wpad.dat (ie do). Now, i think, if the search domain is configured correctly, the name server will give the correct address and make the request.


thanks again

more options

I have a dns entry where http://wpad/wpad.dat and wpad.my.company/wpad.dat both resolve correctly. Also have a DHPC 252 entry, although I understand that Firefox and Chrome do not use DHCP.

The search domain, not quite sure what setting your referring to with this. Please elaborate.

dja2112

more options

What is wrong with using the manual proxy setup? If you do not need to use the proxy somewhere, you simply switch to "no proxy", or exclude that address from using the proxy.

more options

Have to many computers to manually configure.