Artur,
[cc'ing Amaury]
Am 2021-06-07 16:46, schrieb Artur:
However the only difference is the 443 port explicitly specified in the
later request.
I am not sure it's something specific to 2.4.0, but I've never seen it
before.
Is it an expected behaviour ? If so, how can I change my acls to
correct
it ?
I encountered the same issue (incidentally also with socket.io). It's
happening for WebSockets via HTTP/2. These are newly supported starting
with HAProxy 2.4. The "broken" requests are most likely Firefox, while
the working ones are not Firefox. I already have a private email thread
with a few developers regarding this behavior.
Best regards
Tim Düsterhus
