--dTy3Mrz/UPE2dbVg
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jun 30, 2004 at 06:17:40PM +0700, Amadeus wrote:
  | Hello again,
  |=20
  | I recently found out about the wonderful world of "Autoconfiguration" i=
n=20
  | browsers for proxying.
  |=20
  | At the moment I'm entering manually the proxy to all cleint browsers, w=
hich=20
  | is a headache.
  |=20
  | Following many sources I have tried the following:
  |=20
  | wpad.dat on wpad.domain.org
  |=20
  | (specifying the script manually works, so the script is not a problem)
  |=20
  | dhcpd.conf:
  | option wpad code 252 text;
  | option wpad "http://wpad.domain.org/wpad.dat"
  |=20
  | dns:
  | wpad.domain.org

I have been successfully using WPAD for a long time,
via DNS only.  My Windows hosts do get their IP address,
domain-name, DNS servers (etc) from DHCP though.


  | Trying to retrieve:
  | http://wpad.domain.org/wpad.dat
  |=20
  | is successful manually. Using the IP works as well.

Are you sending your domain name via DHCP;
	options domain-name "domain.org";
Is there a "wpad" entry in the domain that the Windows host is in?



  | I even added the following in httpd.conf for apache:
  |=20
  | AddType application/x-ns-proxy-autoconfig .dat

I didn't need to bother with that.

You _may_ need to ensure that the web server is setup as
a HTTP/1.0 "real IP" address server not a HTTP/1.1 virtual
server.


  | All of which fails to work.
  |=20
  | Checking apache's logs, the wpad.dat file is never even queried.
  |=20
  | Any ideas what to do?

tcpdump ?

--dTy3Mrz/UPE2dbVg
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (NetBSD)

iD8DBQFA4zAqpBhtmn8zJHIRArVZAJ432OwRSBqP+ZuAZrUgzUbma1TWMwCeMa+6
r7JSmwU3RZH8Cx7pOeAtvUk=
=DBXO
-----END PGP SIGNATURE-----

--dTy3Mrz/UPE2dbVg--