搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

Removing firefox proxy settings does not work until a restart?

  • 3 个回答
  • 3 人有此问题
  • 1 次查看
  • 最后回复者为 Dimpl

more options

When I transfer from my work network (with a proxy server) to my home network (no server), I have to restart the browser before it realizes that there is no proxy server that it has to authenticate with. Until I do this, (re)loading pages gives me an error.

However, when going the other way, it smoothly recognises that there is a server, and no restart is required to continue browsing

I have automatic proxy settings enabled. I have tried selecting 'no proxy server', but I still need to restart firefox for this to work.

When I transfer from my work network (with a proxy server) to my home network (no server), I have to restart the browser before it realizes that there is no proxy server that it has to authenticate with. Until I do this, (re)loading pages gives me an error. However, when going the other way, it smoothly recognises that there is a server, and no restart is required to continue browsing I have automatic proxy settings enabled. I have tried selecting 'no proxy server', but I still need to restart firefox for this to work.

被采纳的解决方案

Please update to the current Firefox 22.0 release.

  • Help > About Firefox

The Firefox 21 version that you currently run is no longer supported with security updates.

  • It is important to update Firefox and add-ons to the latest version to get all security fixes.

定位到答案原位置 👍 1

所有回复 (3)

more options

hello, is this only affecting secure pages (starting with https://) and does it work when you press ctrl-shift-r after the change in order to reload the page?

more options

选择的解决方案

Please update to the current Firefox 22.0 release.

  • Help > About Firefox

The Firefox 21 version that you currently run is no longer supported with security updates.

  • It is important to update Firefox and add-ons to the latest version to get all security fixes.

more options

Thanks cor-el,

I believe my firefox autoupdated this morning, and the bug is gone :)