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

[jira] [Comment Edited] (TS-3963) Response headers are not completely transferred

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

Bryan Call edited comment on TS-3963 at 10/27/15 11:03 PM:
-----------------------------------------------------------

[~maskit]
The patch removes limits on total header size (doesn't drop headers on the frame boundary), but there is a limit on single header size of 16KB.   I am working on another patch to have headers span multiple frames to get over the 16KB limit on a single header.


was (Author: bcall):
[~maskit]
That patch will not drop headers and will allow a max header size of 16KB.   I am working on another patch to have headers span multiple frames.

> Response headers are not completely transferred
> -----------------------------------------------
>
>                 Key: TS-3963
>                 URL: https://issues.apache.org/jira/browse/TS-3963
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: HTTP/2
>            Reporter: Masakazu Kitajo
>             Fix For: 6.1.0
>
>         Attachments: ts-3963.diff
>
>
> TS loses one response header (one pair of header name and its value) per requiring a CONTINUATION frame.
> You can see the behavior by sending many response headers from an origin server. It happens when the total size of the headers is over 4KB.
> It seems that field_iter in http2_write_header_fragment() incorrectly steps forward.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)