You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Masakazu Kitajo (JIRA)" <ji...@apache.org> on 2015/10/22 17:35:27 UTC

[jira] [Commented] (TS-3847) Rejects Dynamic Table Size if it does not appear at the beginning of the first header block

    [ https://issues.apache.org/jira/browse/TS-3847?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14969318#comment-14969318 ] 

Masakazu Kitajo commented on TS-3847:
-------------------------------------

I think the point is the order, but not the number of dynamic table size update.

In the h2spec test,
The header block contains some header fields and two dynamic table size updates. This is valid.
The updates appear AFTER the header fields. This is not valid.

"This dynamic table size update MUST occur *at the beginning of the first header block* following the change to the dynamic table size. In HTTP/2, this follows a settings acknowledgment (see Section 6.5.3 of \[HTTP2\])."

> 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
>             Fix For: 6.1.0
>
>
> 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)