Difference between revisions of "Features/Automatic Proxy Settings"
Line 21: | Line 21: | ||
(PAC and WPAD) for testing purposes. | (PAC and WPAD) for testing purposes. | ||
− | For testing a proxy in XO you can go to: [http://wiki.sugarlabs.org/go/Features/Proxy_Settings Features/Proxy Settings] | + | For testing a proxy in XO you can go to: [http://wiki.sugarlabs.org/go/Features/Proxy_Settings#How_To_Test Features/Proxy Settings] |
== Benefit to Sugar == | == Benefit to Sugar == |
Revision as of 08:49, 7 January 2013
Summary
Allow the user to setup transparent Proxy service.
Owner
Current status
- Targeted release: 0.98
- Last updated: 2013-01-07
- Percentage of completion: 80%
Detailed Description
Sugar deployments and users need to be able to set a proxy to access some network services.
In this entry you can learn a way of configuring automatic proxy server (PAC and WPAD) for testing purposes.
For testing a proxy in XO you can go to: Features/Proxy Settings
Benefit to Sugar
See Detailed Description.
Scope
It's not directly related to XO, it's just a part for building an environment for automatic proxy testing in XO
PAC - Proxy Auto Config
PAC method for proxy is very simple. You have to create a web-accessible file with special syntax in which you include proxy server data. This example works with Apache server. You can take a look to Bibliograpy for more info about PAC file configuration and installation in other webservers.
Steps:
- Create .htaccess file and add the following content:
AddType application/x-ns-proxy-autoconfig .pac
- Create PAC file and add the following content:
function FindProxyForURL(url, host) { return "PROXY PROXY_SERVER_IP_OR_HOSTNAME:PORT"; }
- Upload both file to the same location:
mv proxy.pac /var/www/proxy.pac mv .htaccess /var/www/.htaccess
- Restart apache /etc/init.d/apache2 restart
WPAD - Web Proxy Autodiscovery
Web Proxy Auto-Discovery Protocol, or WPAD, is a technology which aids a web browser in automatically detecting the location of a PAC file using DNS or DHCP.
A browser that supports both DHCP and DNS will first attempt to locate a PAC file using DHCP, and should a DHCP configuration not exist fail-over to DNS WPAD will occur. If neither are configured, a browser will fail open.