Mailinglist Archive: opensuse-bugs (3926 mails)

< Previous Next >
[Bug 679322] zypper doesn't respect some proxy settings, misunderstands others

https://bugzilla.novell.com/show_bug.cgi?id=679322

https://bugzilla.novell.com/show_bug.cgi?id=679322#c11


--- Comment #11 from Dominique Leuenberger <dimstar@xxxxxxxxxxxx> 2011-08-11
13:15:33 UTC ---
(In reply to comment #10)
I can verify too, that the issue with spaces has been fixed.

Thanks for checking

However there are still problems with specifying entire networks.
e.g. 192.168.0.0/16 does not work.
This is supposed to work. What does 'proxy' (from the package libproxy-tools)
give as result? (start it with _PX_DEBUG=1 _MM_DEBUG=1 proxy
http://192.168.15.1/ )

Domains only work when there is an initial dot, like: .example.com
This is correct. There is no other way in identifying otherwise if a host or a
domain is meant. (The example in yast, regarding the settings for the proxy
fields, has the leading dot as well)

I would like to know if firefox uses libproxy to, when it is configured to
"Use
system proxy settings".
Yes, it does (at least the openSUSE packaged version. The upstream downloaded
one does not)

Also Yast creates a file /root/.curlrc with a single entry like this:
Wrong behavior IMHO. curl should use libproxy.

# Changed by YaST2 module proxy 04/08/2011
--proxy "http://localhost:8080";

How does that affect zypper?
Does it override the env variables? Why not a --noproxy parameter?
That depends on the backend used by zypper to download packages I'm afraid
(curl/aria). Up to the zypp-devels to clarify on that one.

--
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.

< Previous Next >