|
Notes |
|
|
(0004151)
|
|
dloper
|
|
2016-11-23 11:25
|
|
Option should allow you to choose between
1) automatic detection which then queries DNS for wpad host,
2) manual settings which allows the user to select type in the IP address and port of the proxy server, or
3) allow the user to specify the connection script manually. |
|
|
|
(0004351)
|
|
user2
|
|
2016-12-12 18:53
|
|
|
We have not received nearly enough feedback with app-upstream-proxy. Does it work for all applications? How about the command line environment (curl, wget, ftp, lftp, etc.)? There must be some apps/services that require more tuning, but nobody has championed finding all the edge cases. |
|
|
|
(0004781)
|
|
dloper
|
|
2017-02-15 12:52
|
|
There is no concept of os-layer proxy support but what can be emulated to appear as such. For example in Windows, proxy support can be specified in Internet Explorer or as settings in the control panel but such settings are not enforced on applications and it is wholly optional for the app to use those settings. Same thing applies on Mac. While this can be made to be a 'standard' of sorts on the platform, there is nothing intrinsic in the IP stack to mandate this. We can make a central proxy settings config in /etc/clearos (perhaps) and then have utilities such as webconfig's apache, marketplace and other apps to have this promulgated. Perhaps a function of clearsync which is aware of apps installed is the way to go.
Then, as a move forward we can simply educate those making apps who require such settings to adopt the paradigm or create a proxy stub driver in their app that taps into these settings on an app-by-app basis. |
|
|
|
(0004791)
|
|
user2
|
|
2017-02-16 09:25
|
|
> While this can be made to be a 'standard' of sorts on the
> platform, there is nothing intrinsic in the IP stack to mandate
> this.
Yes, that's exactly why this feature - 0001111 - has been waiting on feedback for 4 years. Someone needs to review/audit all the apps to see what still needs to be addressed. Though some apps and CLI tools will adhere to the quasi standard environment variables, there are likely some apps that don't.
> We can make a central proxy settings config in
> /etc/clearos (perhaps) and then have utilities such
> as webconfig's apache, marketplace and other apps to
> have this promulgated. Perhaps a function of clearsync
> which is aware of apps installed is the way to go.
The central configuration file already exists - /etc/clearos/upstream_proxy.conf. In addition, the "upstream proxy" event (via clearsync) also already exists and is in use. The Antivirus app uses the "upstream proxy" event to update the /etc/freshclam.conf file with proxy information.
All the underlying aspects of this were done in 2012, so it's now a matter of reviewing/auditing apps. Off the top of my head:
- SpamAssassin rule updates (sa-update)
- wget
- phpMyAdmin: call home to check for news/updates0
- Zarafa web access: web API calls to things like Gravatar
- CUPS: printer drivers downloaded via CUPS engine
- ownCloud
I'm sure there are more. If there is a desire to add support for upstream proxy in the UI without doing an app audit, then feel free to make that call. However, I can almost guarantee apps will be broken in places!
|
|