Generally according to the specification: 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 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.
- is cloned by
-
UNDERTOW-552 HTTP2: HpackDecoder might not throw HPackException although it should
- Resolved