Feature #603
closed
Add proxy support for internal HTTP functions
0%
Description
In some environments it's difficult to pull packages, auto update, etc. because you need to hit a proxy for outbound access. There should be a central advanced configuration item for proxy info, which is used by every function that uses HTTP internally.
Updated by Jim Pingle almost 14 years ago
Every function that makes a remote HTTP/HTTPS call (file_get_contents, fopen, etc) can take a context parameter with proxy info. It's explained here:
http://www.php.net/manual/en/function.stream-context-create.php
http://php.net/manual/en/function.file-get-contents.php
http://php.net/manual/en/function.fopen.php
We'd just need a proxy settings page somewhere (with text explaining that it would be used for these kinds of calls and it is not related to the squid package, etc)
For things done at the OS level, fetch(3) (not fetch(1)) explains the environment variables needed to setup proxy information.
Updated by Ermal Luçi almost 14 years ago
We use curl or xmlrpc for important stuff so those need to have proxy support too.
Updated by Jim Pingle almost 14 years ago
Curl on the CLI has proxy command line arguments, and the PHP module can use curl_setopt() to use proxy options. Looks like our /etc/inc/xmlrpc_client.inc supports proxies also.
Looks pretty well supported all-around.
Updated by Jim Pingle about 12 years ago
- Status changed from New to Feedback
This was done quite a while ago, Proxy Settings are under System > Advanced, on the Misc tab.
Are there any areas that do not respect this value that need fixed yet?
Updated by Chris Buechler about 12 years ago
- Status changed from Feedback to Resolved