Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-156

No http client support for http_proxy_host, http_proxy_port, and configtimeout

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Normal
    • Resolution: Won't Do
    • SERVER 0.4.0
    • SERVER 1.y, SERVER 2.y
    • None

    Description

      On a Ruby master, the "puppet.conf" settings for http_proxy_host, http_proxy_port, and configtimeout were honored for cases where the master made outgoing client requests, e.g., when submitting a report to an external server. See https://github.com/puppetlabs/puppet/blob/master/lib/puppet/network/http/factory.rb.

      The Puppet Server master does not honor any of these settings for client connections that it makes. We should consider whether or not it is valuable to restore this capability.

      Attachments

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. PUP-3666 Replace 'configtimeout' with separate HTTP connect and read timeout settings

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-377 "puppetserver gem" command doesn't work from behind a proxy server

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          New Feature - A new feature of the product, which has yet to be developed. SERVER-449 Expose http-client timeouts from Puppet Server

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Activity

            People

              Unassigned Unassigned
              jeremy.barlow Jeremy Barlow
              Erik Dasher Erik Dasher
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support