Warning, /frameworks/kio/src/kpac/README.wpad is written in an unsupported language. File is not indexed.

0001 Web Proxy Auto Discovery (WPAD)
0002 ===============================
0004 This README is intended for network administrators who want to enable the
0005 users on their network to fully automatically find the proxy settings.
0007 Automatic proxy discovery works in two steps:
0008 1) Find a configuration script
0009 2) Determine a proxy to use by running that script
0011 The configuration script is a "PAC" (JavaScript) file just as in plain Proxy
0012 Auto Configuration as described here:
0013 http://home.netscape.com/eng/mozilla/2.0/relnotes/demo/proxy-live.html
0015 The WPAD part of the process (#1 above) described here is about how to find
0016 this script without having the users enter its URL into the proxy settings.
0017 (All they have to do in a WPAD-enabled network is to select "Automatically
0018 detected script file" in KDE's proxy setup.
0020 There are two alternative ways to discover the PAC script's URL implemented
0021 in KDE:
0023 1. DHCP based autodiscovery
0025         If you are running a DHCP server on your network anyway, you might
0026         want to use this approach; all you have to do is to add the WPAD
0027         option (numeric 252 or hex fc) as a string containing the URL to the
0028         PAC script.
0030         To do so with older versions of ISC dhcpd, add this to
0031         /etc/dhcpd.conf, either globally or just for the subnets you want to
0032         enable WPAD for:
0034         option option-252 "http://example.com/path/to/proxyconfig.pac";
0036         Or, for newer ISC dhcpd versions, add this globally:
0038         option wpad code 252 = text;
0040         and this either globally or for the WPAD subnets:
0042         option wpad "http://example.com/path/to/proxyconfig.pac";
0044         For other DHCP servers, please consult the reference manual on how
0045         to add an option by number if WPAD support is not built-in.
0047 2. DNS based autodiscovery
0049         If you don't run a DHCP server or prefer DNS based discovery, you
0050         need to configure one of your hosts to have the name
0051         wpad.example.com and make sure the PAC script is available as
0052         http://wpad.example.com/wpad.dat If your network consists of several
0053         subdomains, like a.example.com and b.example.com you can either
0054         provide both http://a.example.com/wpad.dat and
0055         http://b.example.com/wpad.dat or just http://example.com/wpad.dat
0056         When a client searches for that script, it will search for a host
0057         named "wpad" in its own domain, then in the next higher level domain
0058         until success or if only the TLD is left (i.e. wpad.com will never
0059         be tried)
0061 Note that DHCP is the preferred approach since it's more flexible than DNS
0062 as it doesn't require a well known host name nor a fixed location
0063 (/wpad.dat) for the PAC script. It is also the first method tried before
0064 resorting to DNS, so if you use DNS there will be a noticeable delay of 5
0065 seconds while waiting for a DHCP reply.
0067 However, DHCP requires a helper program, kpac_dhcp_helper to be installed
0068 suid root. If you consider this a security problem, just delete that program
0069 or remove its suid permissions and use DNS instead. If the helper cannot
0070 execute as root, the 5 seconds delay will also go away.
0072 If you have further questions or comments, please contact me: Malte
0073 Starostik <malte@kde.org>