TestSlaveGlobalDisableHttp2-0:bootstrap-monitor EXITED
TestSlaveGlobalDisableHttp2-0:certificate_authority-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-0:crond-{hash} RUNNING
TestSlaveGlobalDisableHttp2-0:monitor-httpd-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-0:monitor-httpd-graceful EXITED
TestSlaveGlobalDisableHttp2-1:6tunnel-11080-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:6tunnel-11443-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:6tunnel-12080-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:6tunnel-12443-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:6tunnel-26011-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:6tunnel-26012-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:bootstrap-monitor EXITED
TestSlaveGlobalDisableHttp2-1:certificate_authority-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:crond-{hash} RUNNING
TestSlaveGlobalDisableHttp2-1:crond-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:frontend-caddy-safe-graceful EXITED
TestSlaveGlobalDisableHttp2-1:frontend-nginx-safe-graceful EXITED
TestSlaveGlobalDisableHttp2-1:frontend_caddy-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:frontend_nginx-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:monitor-httpd-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:monitor-httpd-graceful EXITED
TestSlaveGlobalDisableHttp2-1:trafficserver-{hash}-on-watch RUNNING
TestSlaveGlobalDisableHttp2-1:trafficserver-reload EXITED
watchdog:watchdog RUNNING
-
Łukasz Nowak authored
One of solutions for random 502 errors from caddy is to fully disable HTTP2 protocol ( https://github.com/mholt/caddy/issues/1080 ) We run Caddy with HTTP2 enabled by default, as we can enable/disable it per each slave, but in some environments it might be just better to fully avoid HTTP2 codepaths in Caddy. /reviewed-on nexedi/slapos!495
b1d87ee2