http://bugzilla.opensuse.org/show_bug.cgi?id=991680
http://bugzilla.opensuse.org/show_bug.cgi?id=991680#c10
--- Comment #10 from Michael Andres
So company ABS (let's say the use 'abs.com' in their NO_PROXY) matching on tailing chars would mean this company can't reach 'fabs.com'; this sounds like way too many things that can break even worse - 'ABS" would just configure .abs.com and be done with it.
The user experience however seems to be different. You configure 'suse.de' and it works for wget and curl, but not for zypper:
http_proxy=http://proxy.suse.de:3128/ no_proxy='localhost, 127.0.0.1, suse.de'
$ proxy http://www.suse.de # what zypper gets from libsolv http://proxy.suse.de:3128/ http://proxy.suse.de
$ wget http://www.suse.de Resolving www.suse.de (www.suse.de)... i.e. direct://
$ curl -v http://www.suse.de * Connected to www.suse.de... i.e. direct://
Wget probably uses the libproxy ENVVAR module which matches '*suse.de' (far more than you actually wanted, but who actually recognizes this...). Curl matches 'suse.de|*.suse.de', which might be 'lazy and weird' ;), but is probably close to what you actually wanted. Only poor zypper uses the libproxy SYSCONFIG module, which matches just 'suse.de' if you missed the leading dot. AFAIR the idea of the SYSCONFIG module was to let changes to sysconfig/proxy take effect immediately. Otherwise you had to logout and login again or to re-evaluate /etc/profile in order to get the right environment variables. The question is whether the SYSCONFIG module could/should be more relaxed (like curl, which is what zypp uses)? Otherwise the bug would be INVALID as the dot is needed (unless you use curl directly). -- You are receiving this mail because: You are on the CC list for the bug.