The following issue has been filed in JIRA to track the problem with
an HTTP/1.0 response without a Content-Length header:
https://bugs.openjdk.java.net/browse/JDK-8207966
-Chris.
> On 20 Jul 2018, at 08:38, Severin Gehwolf wrote:
>
> Adding net-dev
>
> On Fri, 2018-07-20 at 08:52 +0200,
The initial value for the directional parameter SETTINGS_MAX_CONCURRENT_STREAMS,
in the direction from the server to the client, max concurrent
client-initiated streams, is incorrectly limited to 100, when there
should be no initial limit. Note, the client retains its, configurable,
limit of 100 s
