Hi Willy,
On 15/04/2023 22:08, Willy Tarreau wrote:
And indeed, this issue appeared with this commit in 1.9-dev10 4 years ago:
746fb772f ("MEDIUM: mux_h2: Always set CS_FL_NOT_FIRST for new
conn_streams.")
So it makes h2 behave like the second and more H1 requests which are silent
about this. We overlooked this specificity, it would need to be rethought a
little bit I guess.
Willy
Thanks for looking into this - at least I know its not an issue with our
config.
Just to give you some background: This backend is a development/test
server so its not always powered on.
That's why we return a friendly 503 error so that people know the reason
why the backend is not available.
I did look at trying to workaround this using a backup server to serve
my 503 if we can't connect to the primary.
However I don't want to introduce a check as this server is down quite a
lot of the time by design and I don't want HAProxy reporting it as a
problem when it isn't.
For now we're just going to stick with HTTP/1.1, but if there's anything
I can do to assist in fixing this please let me know. Unfortunately I'm
not up to speed on the internals of HTTP/2 at all.
Regards,
Nick
