Re: Chained http -> http frontends: http/2 error 400 vs http/1.1 error 502

2019-03-01 Thread Christopher Faulet
Le 01/03/2019 à 14:36, Jarno Huuskonen a écrit : Hi, Pinging this thread incase if this an actual error/bug and not a configuration error. (current 2.0-dev1-8dca19-40 2019/03/01 sends 400 error to client when http/2 is used). Hi Jarno, It is not an expected behavior, of course. And after a

Re: Chained http -> http frontends: http/2 error 400 vs http/1.1 error 502

2019-03-01 Thread Jarno Huuskonen
Hi, Pinging this thread incase if this an actual error/bug and not a configuration error. (current 2.0-dev1-8dca19-40 2019/03/01 sends 400 error to client when http/2 is used). -Jarno On Sat, Feb 02, Jarno Huuskonen wrote: > (This is kind of related to this thread: >

Re: ACL, map: restrict access for dynamic hostname to some specific IPs

2019-03-01 Thread gdelafond+haproxy
> On 9 Jan 2019, at 11:06, gdelafond+hapr...@aquaray.com wrote: > > Hello, > > I try to understand how to use the -M ACL flag. > > From the documentation : > > The "-M" flag allows an ACL to use a map file. If this flag is set, the file > is > parsed as two column file. The first column

Re: regtest, response lenght check failure for /reg-tests/http-capture/h00000.vtc with HTX enabled, using 2.0-dev1

2019-03-01 Thread Christopher Faulet
Le 26/02/2019 à 21:29, PiBa-NL a écrit : Hi List, Christopher, With 2.0-dev1-6c1b667 and 2.0-dev1-12a7184 i get the 'failure' below when running reg-tests with HTX enabled. (without HTX the test passes) Seems this commit made it return different results: