https://bugzilla.novell.com/show_bug.cgi?id=679322
https://bugzilla.novell.com/show_bug.cgi?id=679322#c15
--- Comment #15 from Dominique Leuenberger
# no_proxy='192.168.0.0/16' proxy 192.168.1.100 direct:// Correct
# no_proxy='192.168.0.0-192.168.255.255' proxy 192.168.1.100 direct:// This form of proxy ignore is currently not supported by libproxy, so I would rate the result as rather 'random'
http://code.google.com/p/libproxy/wiki/IgnorePatterns
# no_proxy='192.168.1.100' zypper ref -r update Repository 'update' is up to date. Specified repositories have been refreshed.
# no_proxy='192.168.0.0/16' zypper ref -r update Download (curl) error for 'ftp://192.168.1.100/openSUSE_11.4/update/repodata/repomd.xml': Error code: Unrecognized error Error message: Empty reply from server
that is actually not libproxy's fault then!
# no_proxy='192.168.0.0/16' curl -v ftp://192.168.1.100/openSUSE_11.4/update/repodata/repomd.xml * About to connect() to proxy localhost port 8080 (#0) * Trying ::1... Connection refused * Trying 127.0.0.1... connected * Connected to localhost (127.0.0.1) port 8080 (#0)
GET ftp://192.168.1.100/openSUSE_11.4/update/repodata/repomd.xml HTTP/1.1 User-Agent: curl/7.21.2 (x86_64-unknown-linux-gnu) libcurl/7.21.2 OpenSSL/1.0.0c zlib/1.2.5 libidn/1.15 libssh2/1.2.7 Host: 192.168.1.100:21 Accept: */* Proxy-Connection: Keep-Alive
... Then the proxy fails to complete the request. The same happens with no_proxy='192.168.0.0-192.168.255.255' It seems that curl does not understand networks in $no_proxy. I hope I am not getting annoying, but the update may not fix the reporter's problem.
Curl does not use libproxy to my knowledge (at least curl is no linked against libproxy) so apparently somewhen we were lead off track of the initial issue. ==> Seems zypp maintainer need to pick it up from here again then. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.