HAProxy 1.8使用tcp请求检查延迟延迟延迟http/2(h2)请求

HAProxy 1.8使用tcp请求检查延迟延迟延迟http/2(h2)请求,haproxy,Haproxy,使用HAProxy 1.8,我想减慢某些流量。当通过HTTP 1.1进行测试时,这一切都可以工作。但是,一旦在HAProxy中启用http/2(h2),10秒延迟就不再生效。如何延迟h2请求 frontend web bind [...] alpn h2,http/1.1 tcp-request inspect-delay 10s tcp-request content accept if WAIT_END [...] 我正在使用curl进行测试: time curl -I '

使用HAProxy 1.8,我想减慢某些流量。当通过HTTP 1.1进行测试时,这一切都可以工作。但是,一旦在HAProxy中启用http/2(h2),10秒延迟就不再生效。如何延迟h2请求

frontend web
  bind [...] alpn h2,http/1.1
  tcp-request inspect-delay 10s
  tcp-request content accept if WAIT_END
  [...]
我正在使用curl进行测试:

time curl -I 'https://[url]/' -v
*   Trying 10.233.1.97...
* TCP_NODELAY set
* Connected to [url] (10.233.1.97) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
[...]
* ALPN, server accepted to use h2
[...]
* Using HTTP2, server supports multi-use
* Connection state changed (HTTP/2 confirmed)
* Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0
* Using Stream ID: 1 (easy handle 0x7fd3f5808200)
> GET / HTTP/2
> Host: [...]
> User-Agent: curl/7.64.1
> Accept: */*
>
* Connection state changed (MAX_CONCURRENT_STREAMS == 100)!
< HTTP/2 411
HTTP/2 411
< content-type: text/html; charset=us-ascii
content-type: text/html; charset=us-ascii
< server: Microsoft-HTTPAPI/2.0
server: Microsoft-HTTPAPI/2.0
< date: Thu, 02 Apr 2020 19:18:22 GMT
date: Thu, 02 Apr 2020 19:18:22 GMT
< content-length: 344
content-length: 344

<
* Excess found in a non pipelined read: excess = 344 url = / (zero-length body)
* Connection #0 to host app.cloudbilling.nl left intact
* Closing connection 0
curl -I 'https://[url]/' -v  0.02s user 0.01s system 28% cpu 0.101 total
time curl-I'https://[url]/'-v
*正在尝试10.233.1.97。。。
*TCP_节点集
*已连接到[url](10.233.1.97)端口443(#0)
*阿尔卑斯山,提供h2
*ALPN,提供http/1.1
[...]
*ALPN,服务器接受使用h2
[...]
*使用HTTP2,服务器支持多用途
*连接状态已更改(HTTP/2已确认)
*升级后正在将流缓冲区中的HTTP/2数据复制到连接缓冲区:len=0
*使用流ID:1(易处理0x7fd3f5808200)
>GET/HTTP/2
>主持人:[……]
>用户代理:curl/7.64.1
>接受:*/*
>
*连接状态已更改(最大并发流==100)!