-
Bug
-
Resolution: Done
-
Major
-
10.0.0.CR1
-
None
According to RFC7540 frame types DATA, PRIORITY and HEADERS are associated with particular data stream, therefore if its stream id is 0 this should be processed as PROTOCOL_ERROR.
Similarly frames of types GOAWAY and SETTINGS must not be associated with particular stream id other than 0, if so then PROTOCOL_ERROR should be raised.
With current implementation this requirement is not checked causing discrepation against RFC specification.
- clones
-
JBEAP-1108 HTTP2 stream ID is not checked for some frame types
- Closed