[
https://issues.apache.org/jira/browse/TS-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14699786#comment-14699786
]
Bryan Call commented on TS-3847:
--------------------------------
I took a look at this on Saturday and it looks like there is a header block to
change the table size to 0 and then another header block to change the size to
4096. I believe this is valid and should clear the dynamic table according to
the RFC.
> Rejects Dynamic Table Size if it does not appear at the beginning of the
> first header block
> -------------------------------------------------------------------------------------------
>
> Key: TS-3847
> URL: https://issues.apache.org/jira/browse/TS-3847
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
> Reporter: Masaori Koshiba
>
> Section 4.2 of RFC 7541(HPACK), says that dynamic table size update MUST
> occur at the beginning of the first header block following the changes to the
> dynamic table size.
> {code}
> ===============================================================================
> Failed tests
> ===============================================================================
> 4.3. Header Compression and Decompression
> × Encodes Dynamic Table Size Update (RFC 7541, 6.3) after common header
> fields
> - The endpoint MUST terminate the connection with a connection error of
> type COMPRESSION_ERROR.
> Expected: GOAWAY frame (ErrorCode: COMPRESSION_ERROR)
> Connection close
> Actual: DATA frame (Length: 5991, Flags: 1)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
