zypper does not consider NO_PROXY variable

This document (000019675) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 15 SP1

Situation

The domains defined with the variable NO_PROXY in /etc/sysconfig/proxy are not being accepted as domains.

For example:

PROXY_ENABLED = "yes"
NO_PROXY = "localhost, 127.0.0.1, admin.sused.com , suse.com"

The values suse.com and admin.sused.com are not considered to be domains. The hosts with domains suse.com and admin.sused.com continue to access the proxy.

Resolution

To allow "noproxy" access to the hosts with domains suse.com or admin.sused.com, the configuration in /etc/sysconfig/proxy must be changed to:

PROXY_ENABLED = "yes"
NO_PROXY = "localhost, 127.0.0.1, .admin.sused.com , .suse.com"

Domains set in the NO_PROXY variable must start with a leading "." , otherwise they are not accepted as domains.

Cause

Libproxy is not able to evaluate the NO_PROXY setting without leading dots.

Status

Reported to Engineering

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.