[jboss-jira] [JBoss JIRA] (WFLY-5445) HTTP2: HpackDecoder might not throw HPackException although it should
Jan Stourac (JIRA)
issues at jboss.org
Thu Oct 1 09:28:00 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jan Stourac moved JBEAP-1202 to WFLY-5445:
------------------------------------------
Project: WildFly (was: JBoss Enterprise Application Platform)
Key: WFLY-5445 (was: JBEAP-1202)
Workflow: GIT Pull Request workflow (was: CDW v1)
Component/s: Web (Undertow)
(was: Web (Undertow))
Target Release: (was: 7.0.0.GA)
Affects Version/s: 10.0.0.CR2
(was: 7.0.0.DR11 (Alpha))
> HTTP2: HpackDecoder might not throw HPackException although it should
> ---------------------------------------------------------------------
>
> Key: WFLY-5445
> URL: https://issues.jboss.org/browse/WFLY-5445
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.CR2
> Reporter: Jan Stourac
> Assignee: Stuart Douglas
> Priority: Minor
>
> Generally according to the [specification|https://tools.ietf.org/html/rfc7540#section-4.3]: In case when client sends corrupted header data to server - like incomplete header data - causing that server cannot decompress them properly, server should close connection with "COMPRESSION_ERROR" connection-error type.
> Current implementation of [HpackDecoder.java|https://github.com/undertow-io/undertow/blob/master/core/src/main/java/io/undertow/protocols/http2/HpackDecoder.java] is although quite benevolent in such cases causing that connection is terminated later on with "PROTOCOL_ERROR" connection-error type.
> This is probably no big problem and actually is not big issue as connection is actually terminated although with wrong error type, but it is violation against specification.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list