Re: double // after domain causes ERR_HTTP2_PROTOCOL_ERROR after upgrade to 2.4.3

2021-08-20 Thread Willy Tarreau
Hi all, On Fri, Aug 20, 2021 at 02:52:32PM +0300, Jarno Huuskonen wrote: > Hi, > > On 8/20/21 2:20 PM, Lukas Tribus wrote: > > On Fri, 20 Aug 2021 at 13:08, ??? wrote: > > > > > > double slashes behaviour is changed in BUG/MEDIUM: > > > h2: match absolute-path not path-absolute for

Re: double // after domain causes ERR_HTTP2_PROTOCOL_ERROR after upgrade to 2.4.3

2021-08-20 Thread Jarno Huuskonen
Hi, On 8/20/21 2:20 PM, Lukas Tribus wrote: On Fri, 20 Aug 2021 at 13:08, Илья Шипицин wrote: double slashes behaviour is changed in BUG/MEDIUM: h2: match absolute-path not path-absolute for :path · haproxy/haproxy@46b7dff (github.com) Actually, I think the patch you are referring to

Re: double // after domain causes ERR_HTTP2_PROTOCOL_ERROR after upgrade to 2.4.3

2021-08-20 Thread Lukas Tribus
On Fri, 20 Aug 2021 at 13:08, Илья Шипицин wrote: > > double slashes behaviour is changed in BUG/MEDIUM: > h2: match absolute-path not path-absolute for :path · haproxy/haproxy@46b7dff > (github.com) Actually, I think the patch you are referring to would *fix* this particular issue, as it was

Re: double // after domain causes ERR_HTTP2_PROTOCOL_ERROR after upgrade to 2.4.3

2021-08-20 Thread Илья Шипицин
double slashes behaviour is changed in BUG/MEDIUM: h2: match absolute-path not path-absolute for :path · haproxy/haproxy@46b7dff (github.com) however, Tim submitted several "normalization" patches recently. as

Re: double // after domain causes ERR_HTTP2_PROTOCOL_ERROR after upgrade to 2.4.3

2021-08-20 Thread Jarno Huuskonen
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//

double // after domain causes ERR_HTTP2_PROTOCOL_ERROR after upgrade to 2.4.3

2021-08-20 Thread Olaf Buitelaar
Dear Readers, 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//some/path/ https://www.haproxy.org// the browser gives a