Feature #36854: Use HTTP/2 on content proxies to connect to Foreman - Installer - Foreman

Actions

Copy link

Feature #36854

closed

Use HTTP/2 on content proxies to connect to Foreman

Added by Ewoud Kohl van Wijngaarden about 1 year ago. Updated about 1 year ago.

Status:

Closed

Priority:

Normal

Assignee:

Ewoud Kohl van Wijngaarden

Category:

Foreman modules

Target version:

Difficulty:

Triaged:

Bugzilla link:

2152709

Pull request:

https://github.com/theforeman/puppet-foreman_proxy_content/pull/442

Fixed in Releases:

Foreman - 3.9.0

Found in Releases:

Red Hat JIRA:

Description

The HTTP/1.1 protocol can cause TCP race conditions when using keepalive. https://iximiuz.com/en/posts/reverse-proxy-http-keep-alive-and-502s/ does a good job of describing this. HTTP/2 doesn't use keepalive but instead has multiplexing of multiple streams together with a control channel. Testing shows this to be much more reliable, especially at higher concurrency.

Actions

Copy link

Updated by The Foreman Bot about 1 year ago

Status changed from New to Ready For Testing
Assignee set to Ewoud Kohl van Wijngaarden
Pull request https://github.com/theforeman/puppet-foreman_proxy_content/pull/442 added