Hello,
On Fri, Mar 01, Christopher Faulet wrote:
> 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).
> >
>
> 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.
Testing with 2.0-dev2(2.0-dev2 2019/03/26) I get kind of strange results
with http2:
- curl seems to retry in a infinite loop
- firefox tries few times with both H2 / HTTP1.1 and then shows
"Secure Connection Failed"
- chrome tries few times (3 times w/H2 and 3 times w/HTTP/1.1) and
then shows "ERR_SPDY_SERVER_REFUSED_STREAM"
(With HTTP/1.1 all three show 502 error page).
(Also the vtest attached to the start of this thread shows refused
stream).
Here's the test config:
defaults
mode http
option http-use-htx
timeout connect 1s
timeout client 2s
timeout server 4s
timeout tarpit 3s
listen HTTPS_in
mode http
bind 127.0.0.1:8443 ssl crt common.pem alpn h2,http/1.1
server tmpserver abns@proc1 send-proxy-v2
frontend fe
bind abns@proc1 accept-proxy
http-request reject if TRUE
default_backend be
backend be
server h1srv 127.0.0.1:8082
listen H2_server
bind 127.0.0.1:8082
--
Jarno Huuskonen - System Administrator | jarno.huuskonen atsign uef.fi
