Jira (PUP-8246) Consolidate http client connection implementations

[Josh Cooper (JIRA)]

Josh Cooper created an issue

Puppet / PUP-8246 Consolidate http client connection implementations Issue Type: Task Assignee: Unassigned Created: 2017/12/13 11:24 AM Priority: Normal Reporter: Josh Cooper This ticket is a result of PUP-7482. Puppet does not allow callers to specify which CA certs should be trusted when making SSL connections (see PUP-5069). As a result, there are three places where we create SSL connections, and configure the X509::Store: 1. puppet/network/http/factory 2. puppet/util/http_proxy 3. puppet/forge/repository There are several inconsistencies as a result: 1. persistent connections are used for 1, but not 2 2. We send "Ruby" as the user-agent for 2 3. We don't send the X-PUPPET-VERSION header for 2 4. 1 and 2 handle proxy settings differently. Add Comment

This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db)

[Josh Cooper (JIRA)]

Josh Cooper updated an issue

Puppet / PUP-8246 Consolidate http client connection implementations

Change By: Josh Cooper Sprint: Platform Core KANBAN

Add Comment

This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)

[Josh Cooper (JIRA)]

[Josh Cooper (JIRA)]

Josh Cooper commented on PUP-8246

Re: Consolidate http client connection implementations The work required to do this has been split into different tickets in this epic, so this ticket can be closed.

Add Comment