Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-2172

Don't use an http proxy when connecting to localhost

    Details

    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      If an HTTP proxy is configured either in puppet settings or the HTTP_PROXY_* environment variables, then puppet will not use the proxy when connecting to localhost or 127.0.0.1. This behavior can be modified by changing the no_proxy puppet setting or the NO_PROXY environment variable.
      Show
      If an HTTP proxy is configured either in puppet settings or the HTTP_PROXY_* environment variables, then puppet will not use the proxy when connecting to localhost or 127.0.0.1. This behavior can be modified by changing the no_proxy puppet setting or the NO_PROXY environment variable.

      Description

      We had a PE site which had set the http_proxy_{port,host} settings for PMT usage, which had the unintended consequence that all puppet master http connections went through the proxy, including those to the dashboard for node lookups. When something (not yet identified) changed in the network/proxy configuration, these lookups failed causing all agent runs to fail.

      This raises the question about whether it ever makes sense for the master to use a proxy for connections to localhost.

      We've considered two approaches here:
      1) add a new setting for http proxy exclusions. This could be set to, e.g. localhost;*.internal.lan, etc.
      2) never using the proxy settings when talking to localhost

      There may be some other approaches that would work as well.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                josh Josh Cooper
                Reporter:
                kylo Kylo Ginsberg
                QA Contact:
                Erik Dasher
              • Votes:
                1 Vote for this issue
                Watchers:
                11 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support