[
https://issues.apache.org/jira/browse/TS-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14694588#comment-14694588
]
ASF GitHub Bot commented on TS-3752:
------------------------------------
Github user masaori335 commented on the pull request:
https://github.com/apache/trafficserver/pull/276#issuecomment-130510960
Result of h2spec with this patch.
```
...
68 tests, 65 passed, 1 skipped, 2 failed
===============================================================================
Failed tests
===============================================================================
5.3. Stream Priority
5.3.1. Stream Dependencies
× Sends HEADERS frame that depend on itself
- The endpoint MUST treat this as a stream error of type
PROTOCOL_ERROR
Expected: GOAWAY frame (ErrorCode: PROTOCOL_ERROR)
RST_STREAM frame (ErrorCode: PROTOCOL_ERROR)
Connection close
Actual: DATA frame (Length: 5895, Flags: 1)
5.4. Error Handling
5.4.1. Connection Error Handling
× Receives a GOAWAY frame
- After sending the GOAWAY frame, the endpoint MUST close the TCP
connection.
Expected: Connection close
Actual: Error: Connection closed, but did not receive a GOAWAY
Frame.
```
> Problem with larger headers and HTTP/2
> --------------------------------------
>
> Key: TS-3752
> URL: https://issues.apache.org/jira/browse/TS-3752
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
> Reporter: Bryan Call
> Assignee: Masaori Koshiba
> Labels: yahoo
> Fix For: 6.0.0
>
>
> There is a problem when ATS receives a HEADERS or CONTINUATION frame on the
> HEADERS frame and there is no end of header to be decoded. If there is 1
> small header at the beginning of the frame it will work, but if a large
> header either starts at the beginning of the frame or started on the previous
> frame and don't end until the next frame then the decoded_bytes will be 0.
> This will cause a COMPRESSION_ERROR to be send to the client with a GOAWAY
> frame.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
