Bugzilla – Bug 157024
NO_PROXY not honored - Bug since SuSE 7.3
Last modified: 2006-04-07 11:45:03 UTC
Martin Vogt wrote: > > Martin Vogt wrote: > > > > >>> >>> Hello SuSE List, >>> >>> >>> >>> The module YAST software installation, does not use the "no_proxy" variable? >>> >>> I have this problem since SuSE 7.3 >>> >>> >>> >>> regards, >>> >>> >>> >>> Martin >>> >>> >>> >>> >> >> >> >> > > The part in the source is: > > src/media/MediaCurl.cc: > > > > SysConfig cfg( "proxy" ) > > > > if ( cfg.readBoolEntry( "PROXY_ENABLED", false ) ) { > > bool useproxy = true; > > > > std::vector<std::string> nope; > > stringutil::split( cfg.readEntry( "NO_PROXY" ), nope, ", \t" ); > > for ( unsigned i = 0; i < nope.size(); ++i ) { > > // no proxy: if nope equals host, > > // or is a suffix preceeded by a '.' > > string::size_type pos = _url.host().find( nope[i] ); > > if ( pos != string::npos > > && ( pos + nope[i].size() == _url.host().size() ) > > && ( pos == 0 || _url.host()[pos -1] == '.' ) ) { > > D__ << "NO_PROXY: " << nope[i] << " matches host " <<_url.host() << endl; > > useproxy = false; > > break; > > } > > } > > > > the proxy in sysconfig/proxy: > > NO_PROXY="localhost, my.corp.de, 10.136.16.223" > > > > Maybe this needs a tab as seperator ??? > > Although im still not sure if this code segment ist reached at all. > > The code segment is reached. If I set PROXY_ENABLED="no" it works. So I think its a bug. Martin
adjusting summary ;-)
Is this still the case with zypp?
Hm, google tells me that this is something with i18n. Do I need to change something in yast? This was a standard SuSe 10.1b6 installation, done with autoyast2.
No idea - I've not implemented it. I'll take a look what happens there.
Fixed in zypp SVN Revision 2502 (not included in Beta8). Supports exact and subdomain (host foo.bar.de matched by .bar.de). Networks (e.g. "192.168.0.0/24") in NO_PROXY are not supported (I don't know if they are allowed in the NO_PROXY variable at all).
Please retest, if it works on the next avaliable version (RC1). Thanks!
It works for me now and I consider it fixed. If not, just reopen.