Project

General

Profile

Actions

Feature #36854

closed

Use HTTP/2 on content proxies to connect to Foreman

Added by Ewoud Kohl van Wijngaarden 6 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Category:
Foreman modules
Target version:
-
Fixed in Releases:
Found in Releases:

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 #1

Updated by The Foreman Bot 6 months 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
Actions #2

Updated by Ewoud Kohl van Wijngaarden 6 months ago

  • Bugzilla link set to 2152709
Actions #3

Updated by The Foreman Bot 6 months ago

  • Fixed in Releases 3.9.0 added
Actions #4

Updated by Ewoud Kohl van Wijngaarden 6 months ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF