[
https://issues.apache.org/jira/browse/TS-3843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14698367#comment-14698367
]
Masakazu Kitajo commented on TS-3843:
-------------------------------------
{noformat}
SEND[1]: [Lenght: 0, Type: HEADERS(1), Flags: 0, StreamID: 1]
SEND[1]: [Lenght: 26, Type: CONTINUATION(9), Flags: 4, StreamID: 1]
Flags: END_HEADERS
SEND[1]: [Lenght: 0, Type: DATA(0), Flags: 1, StreamID: 1]
Flags: END_STREAM
RECV[0]: [Lenght: 8, Type: GOAWAY(7), Flags: 0, StreamID: 0]
Last-Stream-ID: 1
Error Code: PROTOCOL_ERROR
{noformat}
> Strange framing should be handled as usual
> ------------------------------------------
>
> Key: TS-3843
> URL: https://issues.apache.org/jira/browse/TS-3843
> Project: Traffic Server
> Issue Type: Improvement
> Components: HTTP/2
> Reporter: Masakazu Kitajo
>
> To put all header fields into CONTINUATION frames is not prohibited, however,
> TS treat this framing as a protocol error.
> Though such a framing is inefficient and would not be used by ordinary
> clients, it should be handled in the same way as normal cases. Because it can
> be used for server fingerprinting.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
