Version: unknown (using KDE 3.1.2) Installed from: compiled sources Compiler: gcc version 3.2.2 (PLD Linux) OS: Linux (i686) release 2.4.20 I'm on host wieszak.lan, and there is a file http://wpad.lan/wpad.dat with auto configuration script. Konqueror fails to use it with "automatically detect proxy" setting. IE6 on Windows XP connected to the same network segment detects that proxy.
This is because your domain .lan is only one level. The DNS based WPAD discovery in KDE only traverses up to the second domain level. This is in violation of the WPAD draft indeed. However that draft refers to RFC 1591 for domains to stop at, which is rather obsolete. Seems like I'll have to include a list of known TLDs including CCTLDs etc. to correctly stop (i.e. not try wpad.com, wpad.org, wpad.de etc. but do try wpad.lan) problem is with those countries like UK where the second level domain is also well known, e.g. wpad.co.uk shouldn't be tried either. Any chance you have such a list handy? :-) Three possible workarounds for now: a) add a wpad.wieszak.lan CNAME wpad.lan record and accordingly for every other host (not very good solution indeed) b) add another domain level, i.e. change *.lan to *.my.lan or whatever (not very nice to migrate either) c) use DHCP instead of DNS, no need for well-known names then Regards, -Malte
Subject: kdelibs/kio/misc/kpac CVS commit by malte: CCMAIL: 60885@bugs.kde.org Try to be smart when detecting the most top level domain to traverse to when looking for a host named "wpad". The first domain for which a SOA record exists is the last one tried. Michal, can you please check if this works for you now? Don't crash kded if proyForURL() is called but autoproxy turned off. M +49 -8 discovery.cpp 1.6 M +4 -1 discovery.h 1.2 M +10 -7 proxyscout.cpp 1.3 M +2 -2 proxyscout.h 1.3
I use 3.1.4 (Debian unstable) and it does not work for me either. Any news regarding this (annoying) bug?
Just to try it out, I even set *.my-lan-domain. IN CNAME my.wpad.server. which does not work as well.
Does *NOT* work in 3.1.93 as well.
*** Bug 69631 has been marked as a duplicate of this bug. ***
Mergeing with http://bugs.kde.org/show_bug.cgi?id=69026. Please follow the detailed troubleshooting outlined there to determine if your issue is the result of one of the problems listed there. Also is anyone here having this problem on a multi-homed machine, i.e. one with two network cards that connect to two different networks ? *** This bug has been marked as a duplicate of 69026 ***
Problem still persists on 3.2.2 for me. I'm on the domain "effenberger", and wpad.effenberger is available as host. http://wpad.effenberger/proxy.pac sends a correct proxy.pac file. However, no proxy is being found. Entering the proxy.pac path manually works fine.
Problem still persists on 3.3.1 for me. I'm on the domain "effenberger", and wpad.effenberger is available as host. http://wpad.effenberger/proxy.pac sends a correct proxy.pac file. However, no proxy is being found. Entering the proxy.pac path manually works fine.