Talk:Web Proxy Auto-Discovery Protocol

Update
In order to add some more details on Proxy auto configuration, I have split this page into two, reviving the old Proxy auto-config page. It could be argued that all information conceptually fits into one page. However, this page should then be called "Proxy configuration" or "Proxy auto-config" and discuss the details of all three levels: manual configuration, PAC and WDAP, each adding another layer of automatisation on top of the previous level.

Yaakov Belch

The Site-local options section feels a bit rough (and inappropriate in tone); the second sentence particularly has suffered grammatical/editing errors that have muddied its meaning. I've already changed the _ASCII Italics_ into real italics, but I'm not about to touch the rest since it was precisely what I was trying to find out in the first place. 202.27.216.35 08:00, 21 May 2007 (UTC)


 * The MIME type of the JavaScript configuration file is listed in the article as application/x-ns-proxy-autoconfig; however, I've found one reference that specifies that this is an old, deprecated MIME type and that conforming sites should instead use application/x-javascript-config. David McBride 14:50, 6 September 2007 (UTC)

On the front page it claims Opera supports WPAD, this isn't the case and the author might have been confusing supporting .pac files, which it does support. Plenty of requests on the Opera forum to support this, but they don't seem interested.

Bring back cite-location-part from history: ==Site-local options== RFC 2131 defined the options from 128-254 to be "site local". The meaning of this is that the site's systems administrator - not a software programmer, not a corporate executive at Cisco, not any external body - a Sysadmin of your network to allocate from this space. This is done without involving IANA to avoid the duplication of assignments, and can only be guaranteed so long as your network's administrators are the ones doing this site-local allocation. In later years, it was discerned that perhaps 128-254 options were perhaps a few more than were really necessary (that, and the space from 1-127 was running dry). RFC 3942 redefined the site-local space to be those options from 224 to 254. It is non-reference and improper to continue using option 252 for WPAD, or any other purpose, unless you yourself are the site-local administrator and configured both the server and client to process and consume these options. mabdul 10:24, 9 February 2010 (UTC)

Browser support
The best citation I found on the net was this http://www.msexchangefaq.de/verschiedenes/wpad.htm it is in German, but the table is very informative. It is outdated but newer then the rest I found. Very good is the difference by splitting up the support by the criteria: DHCP, DNS, manual script. We should consider to overtake and update a similar table! mabdul 10:18, 9 February 2010 (UTC)

I haven't found much information about this, but according to Firefox bug 356831, WPAD via DHCP should be supported in Firefox from version 63 onwards. Cmcqueen1975 (talk) 03:07, 21 January 2020 (UTC)