[jboss-jira] [JBoss JIRA] (WFLY-5364) HTTP2 stream ID is not checked for some frame types
[
https://issues.jboss.org/browse/WFLY-5364?page=com.atlassian.jira.plugin....
]
Jan Stourac updated WFLY-5364:
------------------------------
Description:
According to [RFC7540|https://tools.ietf.org/html/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.
was:
According to [RFC7540|https://tools.ietf.org/html/rfc7540] frame types DATA 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.
HTTP2 stream ID is not checked for some frame types
---------------------------------------------------
Key: WFLY-5364
URL: https://issues.jboss.org/browse/WFLY-5364
Project: WildFly
Issue Type: Bug
Components: Web (Undertow)
Affects Versions: 10.0.0.CR1
Reporter: Jan Stourac
Assignee: Stuart Douglas
According to [RFC7540|https://tools.ietf.org/html/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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)