Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

PAC file not working

  • 3 odpowiedzi
  • 12 osób ma ten problem
  • 1 wyświetlenie
  • Ostatnia odpowiedź od liuqx

more options

The firefox is really a fabulous browser, and I really appreciate the brilliant guys working on it. But here's the problem: the PAC file does not seem to be working. This PAC file contains a list of domains needed by the browser to decide which domain should be accessed directly, which domain should be accessed through the proxy server. I've been using ShadowsocksR ( https://github.com/shadowsocksr-backup/shadowsocksr-csharp ), who serves as a HTTP proxy server on 127.0.0.1:1080 with a PAC file(pac.txt), and it works quite well with IE and Edge. However, with firefox, I can not use this proxy server. I've tried another PAC file, proxy.pac on GitHub: https://github.com/breakwa11/gfw_whitelist , which turns out to work properly on IE and Edge(with the first line changed to: var wall_proxy = "PROXY 127.0.0.1:1080; HTTPS 127.0.0.1:1080; SOCKS5 127.0.0.1:1080 ;";), but again, no luck with firefox. When I set the proxy server to 127.0.0.1:1080 directly in firefox, everything was working as it should. But once the PAC file is involved, firefox cannot use the proxy server anymore. I think there might be some problem when firefox parses the PAC file. Any help? Thanks!

Updated: I also pressed Ctrl+Shift+J yesterday, and it showed the pac file had been installed. But firefox just couldn't use proxy server configured in the pac file. Restarting firefox wouldn't help. I tried another browser, Chrome, and the pac file also worked fine in Chrome.

The firefox is really a fabulous browser, and I really appreciate the brilliant guys working on it. But here's the problem: the PAC file does not seem to be working. This PAC file contains a list of domains needed by the browser to decide which domain should be accessed directly, which domain should be accessed through the proxy server. I've been using ShadowsocksR ( https://github.com/shadowsocksr-backup/shadowsocksr-csharp ), who serves as a HTTP proxy server on 127.0.0.1:1080 with a PAC file(pac.txt), and it works quite well with IE and Edge. However, with firefox, I can not use this proxy server. I've tried another PAC file, proxy.pac on GitHub: https://github.com/breakwa11/gfw_whitelist , which turns out to work properly on IE and Edge(with the first line changed to: var wall_proxy = "PROXY 127.0.0.1:1080; HTTPS 127.0.0.1:1080; SOCKS5 127.0.0.1:1080 ;";), but again, no luck with firefox. When I set the proxy server to 127.0.0.1:1080 directly in firefox, everything was working as it should. But once the PAC file is involved, firefox cannot use the proxy server anymore. I think there might be some problem when firefox parses the PAC file. Any help? Thanks! Updated: I also pressed Ctrl+Shift+J yesterday, and it showed the pac file had been installed. But firefox just couldn't use proxy server configured in the pac file. Restarting firefox wouldn't help. I tried another browser, Chrome, and the pac file also worked fine in Chrome.

Zmodyfikowany przez liuqx w dniu

Wybrane rozwiązanie

Solved this problem by setting network.dns.disableIPv6 to true. I don't consider this as a good solution, because pure IPv6 sites can't be accessed.

My ISP provides both IPv4 and IPv6. Obviously firefox has something wrong with the PAC file when IPv6 is enabled. I'm hoping this bug can get fixed as soon as possible! Every browser I've tried works well except for firefox.

Przeczytaj tę odpowiedź w całym kontekście 👍 2

Wszystkie odpowiedzi (3)

more options

It should work - I can’t recall not using it, albeit as a locally stored file. If you do, be sure to use the format in the next example however when entering its URL in Firefox on Windows: file:///c://Users/<user>/pac_file_name.pac ...so mind the 3 forward slashes and the required .pac extension.

When entering a http URL for a local file, http:// would be fine but you may need to configure your server for the proper MIME type. See this page for more info.

There are some other caveats though with regard to .pac files, but I don’t think they apply to your issue. For reference:

  1. isInNet() calls can cause hangs in Firefox and should be avoided or replaced (bug 208287).
  2. Microsoft no longer considers file:// URLs to be valid URLs, causing them to not work in IE and other products when used as such, unless a Windows registry change is applied - this is the EnableLegacyAutoProxyFeatures value.

Let us know if this helps.

more options

But today, I restarted my computer and it worked like a charm! I just can't find a plausible explanation to this, how could this have anything to do with my system? I strongly recommend somebody test the pac file. Anyway, thanks! I'm gonna test firefox for another couple of days, in case it has a relapse and restarting my system doesn't work! You know it worries me when some problems get solved by coincidence, haha

Zmodyfikowany przez liuqx w dniu

more options

Wybrane rozwiązanie

Solved this problem by setting network.dns.disableIPv6 to true. I don't consider this as a good solution, because pure IPv6 sites can't be accessed.

My ISP provides both IPv4 and IPv6. Obviously firefox has something wrong with the PAC file when IPv6 is enabled. I'm hoping this bug can get fixed as soon as possible! Every browser I've tried works well except for firefox.