Le 10/20/21 à 01:24, Björn Jacke a écrit :
Hi,
On 19.10.21 11:06, Christopher Faulet wrote:
Sorry Björn, I missed your reply. It is strange, there is no known bug
in this area for now. There is probably something in the request or
response headers preventing the compression to be enabled.
I found the error: the "compression offload" is not honored in the
default section. This behavior is documented but it slipped from my memory.
What is actually the reason why this is silently ignored when it is set
in the the default section? If someone has a reason to set that in the
default section, why does haproxy ignore it intentionally?
If the support of compression offload shall stay intentionally
unsupported in the default section, then it would be good if this would
trigger a configure check warning, wouldn't it?
Thanks
Björn
Good catch. Indeed, this parameter is ignored in defaults sections. However
there is no warning and the documentation is not really helpful on this point
because it is only mentioned as a side note. I guess it may be more visible.
This parameter is not supported in defaults sections because there is no way to
cancel it in backend sections. I guess we can add a directive to disable the
compression offloading. This way, we will be able to support "compression
offload" in defaults section.
--
Christopher Faulet
