搜索 | 用户支持

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

详细了解

Using system wide proxy setting in Linux

  • 3 个回答
  • 0 人有此问题
  • 689 次查看
  • 最后回复者为 hinko.kocevar

more options

I have the HTTP_PROXY, HTTPS_PROXY and FTP_PROXY (and their lowercase counterparts) exported and then the firefox binary is started from the shell script. The settings in firefox say it will 'Use system proxy settings'. Nevertheless I do not see the proxy being used as I can not access the web pages that need the proxy. The 'about:config' also does not show that firefox picked up any proxy related information from the shell environment.

I know the proxy address is correct because if I use brave browser instead of firefox (same shell script that launches brave) I can reach the web pages behind the proxy as expected.

I have the HTTP_PROXY, HTTPS_PROXY and FTP_PROXY (and their lowercase counterparts) exported and then the firefox binary is started from the shell script. The settings in firefox say it will 'Use system proxy settings'. Nevertheless I do not see the proxy being used as I can not access the web pages that need the proxy. The 'about:config' also does not show that firefox picked up any proxy related information from the shell environment. I know the proxy address is correct because if I use brave browser instead of firefox (same shell script that launches brave) I can reach the web pages behind the proxy as expected.

被采纳的解决方案

If your proxy is set up in the following format: "<proxy_user>:<proxy_password>@<proxy_host>", you have to add a scheme (http://).

定位到答案原位置 👍 1

所有回复 (3)

more options

If the 'Manual proxy configuration' is used instead I can access the web pages behind the proxy. But this is not what I want to do; I would like firefox to pick up the system wide proxy settings.

more options

选择的解决方案

If your proxy is set up in the following format: "<proxy_user>:<proxy_password>@<proxy_host>", you have to add a scheme (http://).

more options

I only have "<proxy_host>:<proxy_port>". Nevertheless adding "http://" in front of it solved the issue for me.

Would be really nice if this was documented somewhere (apologizes if it is , but I couldn't spot it)..