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 quick check, it
is a bug. Instead of catching an error from the server side, we handle
it as an abort from the client.
I have to investigate a bit more because abortonclose seems to be broken
too. And when HTX is enable, the H1 is buggy too.
--
Christopher Faulet
