<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-wrec-wpad" target="https://datatracker.ietf.org/doc/html/draft-ietf-wrec-wpad-01">
   <front>
      <title>Web Proxy Auto-Discovery Protocol</title>
      <author initials="C. E." surname="Perkins" fullname="Charles E. Perkins">
         <organization>Sun Microsystems</organization>
      </author>
      <author initials="J." surname="Cohen" fullname="Josh Cohen">
         <organization>Microsoft Corporation</organization>
      </author>
      <author initials="M." surname="Dunsmuir" fullname="Martin Dunsmuir">
         <organization>RealNetworks, Inc.</organization>
      </author>
      <author initials="P. A." surname="Gauthier" fullname="Paul A. Gauthier">
         <organization>Inktomi Corporation</organization>
      </author>
      <author initials="I." surname="Cooper" fullname="Ian Cooper">
         </author>
      <author initials="J. W. C." surname="M.A." fullname="John W. Cohen M.A.">
         </author>
      <date month="July" day="29" year="1999" />
      <abstract>
	 <t>A mechanism is needed to permit web clients to locate nearby web 
proxy caches. Current best practice is for end users to hand 
configure their web client (i.e., browser) with the URL of an &#x27;auto 
configuration file&#x27;. In large environments this presents a 
formidable support problem.  It would be much more manageable for 
the web client software to automatically learn the configuration 
information for its web proxy settings. This is typically referred 
to as a resource discovery problem.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-wrec-wpad-01" />
   
</reference>
