Hi,
On 8/20/21 1:46 PM, Olaf Buitelaar wrote:
After we upgraded to haproxy version 2.4.3 from 2.4.2 urls with a double
slash after the domain stopped working. We're running the standard
docker image
For example;
https://www.example.com// <https://www.example.com//>
https://www.example.com//some/path/ <https://www.example.com//some/path/>
https://www.haproxy.org// <https://www.haproxy.org//>
the browser gives a ERR_HTTP2_PROTOCOL_ERROR
while on 2.4.2 this worked fine. probably this has something todo with
the mitigations of
https://www.mail-archive.com/[email protected]/msg41041.html
<https://www.mail-archive.com/[email protected]/msg41041.html>
our bind line looks like;
bind *:8443 allow-0rtt ssl crt /usr/local/etc/haproxy/xxx.bundle.pem crt
/usr/local/etc/haproxy/yyy.bundle.pem alpn h2,http/1.1
Generally our backend servers are http1.
Same thing happens to me with 2.4.3 and 2.2.16.
Seems to happen only for https://www.example.com// but not for
https://www.example.com/somepath//something
-Jarno
--
Jarno Huuskonen
