HoneyryderChuck ca75148e86 http/2: do not interpret MAX_CONCURRENT_STREAMS as request cap
a misinterpretation of the spec on http-2-next led to the introduction
of the max_requests option, a cap of requests on a given connection,
which in http/2 case, would be initialized with MAX_CONCURRENT_STREAMS,
which means something else.

This has been fixed already in http-2-next, and this is the summary of
changes required to support it.

The `max_requests` option is kept, as it can still be useful from a user
perspective, but the default in http/2 is now INFINITY, which disables
it effectively. The HTTP/1 cap is bumped to 200, but it may fall as
well soon.
2023-10-13 15:56:10 +01:00
..
2023-08-16 01:08:41 +01:00
2023-10-12 22:39:26 +01:00
2023-09-20 17:57:39 +01:00
2020-10-30 16:19:18 +00:00
2023-09-20 17:57:41 +01:00