netty5

History

Bryce Anderson 7f95506132 Don't send a RST on close of the stream may not have existed (#8086 ) Motivation: When a Http2MultiplexCodec stream channel fails to write the first HEADERS it will forcibly close, and that will trigger sending a RST_STREAM, which is commonly a connection level protocol error. This is because it has what looks like a valid stream id, but didn't check with the connection as to whether the stream may have actually existed. Modifications: Instead of checking if the stream was just a valid looking id ( > 0) we check with the connection as to whether it may have existed at all. Result: We no longer send a RST_STREAM frame from Http2MultiplexCodec for idle streams.	2018-07-05 17:09:23 -07:00
..
src	Don't send a RST on close of the stream may not have existed (#8086 )	2018-07-05 17:09:23 -07:00
pom.xml	[maven-release-plugin] prepare for next development iteration	2018-05-14 11:11:45 +00:00

Bryce Anderson 7f95506132 Don't send a RST on close of the stream may not have existed (#8086 )

Motivation:

When a Http2MultiplexCodec stream channel fails to write the first
HEADERS it will forcibly close, and that will trigger sending a
RST_STREAM, which is commonly a connection level protocol error. This is
because it has what looks like a valid stream id, but didn't check with
the connection as to whether the stream may have actually existed.

Modifications:

Instead of checking if the stream was just a valid looking id ( > 0) we
check with the connection as to whether it may have existed at all.

Result:

We no longer send a RST_STREAM frame from Http2MultiplexCodec for idle
streams.

2018-07-05 17:09:23 -07:00

src

Don't send a RST on close of the stream may not have existed (#8086 )

2018-07-05 17:09:23 -07:00

pom.xml

[maven-release-plugin] prepare for next development iteration

2018-05-14 11:11:45 +00:00