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

[jira] [Comment Edited] (TS-3752) Problem with larger headers and HTTP/2

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

Masaori Koshiba edited comment on TS-3752 at 7/28/15 7:23 AM:
--------------------------------------------------------------

Sorry, I was wrong. It look like there are problems with decoding large header with HPACK.

BTW,  after the commit (6c4c7226ea4d25c084d1d6b97ae6fec262b9f1f3), ATS can't break infinit loop from [Http2ConnectionState.cc#L221|https://github.com/apache/trafficserver/blob/master/proxy/http2/Http2ConnectionState.cc#L221] when ATS recieve large header which is HPACK encoded and over 4096 bytes with default settings.


was (Author: masaori):
Sorry, I was wrong. It look like there are problems with decoding large header with HPACK.

BTW,  after the commit (6c4c7226ea4d25c084d1d6b97ae6fec262b9f1f3), ATS can't break infinit loop from [Http2ConnectionState.cc#L221|https://github.com/apache/trafficserver/blob/master/proxy/http2/Http2ConnectionState.cc#L221] when ATS recieve large header which is HPACK decoded and over 4096 bytes with default settings.

> 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: Bryan Call
>              Labels: yahoo
>             Fix For: 6.1.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)