RHSA-2021:2993

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~

This issue can be mitigated by: 1) Disabling HTTP/2 request support by executing: ~~~ sudo varnishadm param.set feature -http2 ~~~ 2) Disabling backend connection reuse on varnish side, the following rule can be inserted into Varnish configuration: ~~~ sub vcl_backend_fetch { set bereq.http.Connection = "close"; } ~~~