[
https://issues.apache.org/jira/browse/TS-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908637#comment-14908637
]
Bryan Call edited comment on TS-3946 at 9/25/15 8:38 PM:
---------------------------------------------------------
The patch is not correct. Padding is at the end of the frame and taking the
length into account would put the offset somewhere in the middle of the frame
instead of the start of where the headers begin.
was (Author: bcall):
I don't think that is a correct patch. Padding is at the end of the frame and
taking the length into account would put the offset somewhere in the middle of
the frame instead of the start of where the headers begin.
> Invalid pad length in HTTP/2
> ----------------------------
>
> Key: TS-3946
> URL: https://issues.apache.org/jira/browse/TS-3946
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
> Reporter: Leif Hedstrom
> Assignee: Leif Hedstrom
> Fix For: 6.1.0
>
>
> This is an h2spec issue:
> {code}
> 6.1. DATA
> ✓ Sends a DATA frame with 0x0 stream identifier
> ✓ Sends a DATA frame on the stream that is not opend
> × Sends a DATA frame with invalid pad length
> - The endpoint MUST treat this as a connection error of type
> PROTOCOL_ERROR.
> Expected: GOAWAY frame (ErrorCode: PROTOCOL_ERROR)
> RST_STREAM frame (ErrorCode: PROTOCOL_ERROR)
> Connection close
> Actual: RST_STREAM frame (Length: 4, Flags: 0, ErrorCode:
> STREAM_CLOSED)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
