Our webdevs notice clients are no longer receiving pages in gzip
format. One thing that has changed is we have another haproxy server
in the middle and the backed to it is via server send-proxy-v2. If I
skip the middle haproxy server and hit the final servers directly,
then haproxy will properly encode the html pages.
Was running something in 2.8, but upgraded to 3.2.4 and verified still an issue.
Fairly basic:
filter compression
compression algo gzip
compression type text/html text/plain text/css
application/xml application/javascript
application/x-www-form-urlencoded application/json
I can narrow it down to a more complete config and test case if this
is expected to work and not easily reproduced. If this is expect to
fail (known limitation of proxy-v2), is the recommended option to use
http/https instead and set the headers for IP tracking? I prefer
passing original IPs via proxy protocol instead of headers, but that's
only a requirement with tcp.
