tree a986de5f39e204c473f26d7c88bc47fdcffcc864
parent 198b50770d2f2d98a1d399ecb003be28a10ae128
author Willy Tarreau <w@1wt.eu> 1652340281 +0200
committer Willy Tarreau <w@1wt.eu> 1652340598 +0200
encoding latin1

MINOR: mux-h2: report a trace event when failing to create a new stream

There are two reasons we can reject the creation of an h2 stream on the
frontend:
  - its creation would violate the MAX_CONCURRENT_STREAMS setting
  - there's no more memory available

And on the backend it's almost the same except that the setting might
have be negotiated after trying to set up the stream.

Let's add traces for such a sitaution so that it's possible to know why
the stream was rejected (currently we only know it was rejected).

It could be nice to backport this to the most recent versions.