[
https://issues.apache.org/jira/browse/TS-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14908547#comment-14908547
]
Leif Hedstrom edited comment on TS-3946 at 9/25/15 10:25 PM:
-------------------------------------------------------------
Update: This problem actually seems to be intermittent as well. It does get
better with the patch, but now I'm not so sure that it's correct?
Update2: removed the broken patch, but the error is intermittent
was (Author: zwoop):
I have a trivial patch for this, please review:
Update: This problem actually seems to be intermittent as well. It does get
better with the patch, but now I'm not so sure that it's correct?
Update2: removed the broken patch, but the error is intermittent
> 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)
