Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Firefox 67 regression in proxy settings

  • 3 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 n5mx

more options

I have a proxy.pac file I've been using with Firefox for over a year. The proxy.pac is available at https://gist.github.com/magic-lantern/83263e3c1fd251afec8a38d715eefefa I've also attached a screenshot of my Network/Connection Settings configuration.

I frequently use SSH to connect to a remote host, and use the -D option to provide a dynamic proxy to that SSH host. Once I open the dynamic SOCKS5 proxy, I use Firefox to connect to services running on the remote SSH host. For example, http://localhost:8888 which goes through the proxy to the remote host.

As of Firefox 66.0.5 this has always worked great. Just yesterday I updated to 67 and now proxying of localhost/127.0.0.1 no longer works.

Not sure if this is a bug or a feature.

Is there a new way in FF67 to make this work?

I have a proxy.pac file I've been using with Firefox for over a year. The proxy.pac is available at https://gist.github.com/magic-lantern/83263e3c1fd251afec8a38d715eefefa I've also attached a screenshot of my Network/Connection Settings configuration. I frequently use SSH to connect to a remote host, and use the -D option to provide a dynamic proxy to that SSH host. Once I open the dynamic SOCKS5 proxy, I use Firefox to connect to services running on the remote SSH host. For example, http://localhost:8888 which goes through the proxy to the remote host. As of Firefox 66.0.5 this has always worked great. Just yesterday I updated to 67 and now proxying of localhost/127.0.0.1 no longer works. Not sure if this is a bug or a feature. Is there a new way in FF67 to make this work?
附加的畫面擷圖

被選擇的解決方法

Try to set this pref to true on the about:config page.

  • network.proxy.allow_hijacking_localhost = true

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.


  • Bug 1535581 - proxy settings for localhost not obeyed unless network.proxy.allow_hijacking_localhost is set

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
)

從原來的回覆中察看解決方案 👍 1

所有回覆 (3)

more options

選擇的解決方法

Try to set this pref to true on the about:config page.

  • network.proxy.allow_hijacking_localhost = true

You can open the about:config page via the location/address bar. You can accept the warning and click "I accept the risk!" to continue.


  • Bug 1535581 - proxy settings for localhost not obeyed unless network.proxy.allow_hijacking_localhost is set

(please do not comment in bug reports
https://bugzilla.mozilla.org/page.cgi?id=etiquette.html
)

more options

Thanks for pointing out that bug that referenced the exact problem I was having. Seems like a change like that should have been in the release notes - or just more prominent in the notes as I didn't see that change.

more options