[ https://issues.apache.org/jira/browse/TS-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14396283#comment-14396283 ]
Leif Hedstrom commented on TS-3493: ----------------------------------- [~psudaemon] I'd like to propose this for a back port to 5.3.0 as well. This fixes a protocol anomaly where we really don't follow the specs to allow the window size to grow. > Grow window sizes as part of HTTP session setup > ----------------------------------------------- > > Key: TS-3493 > URL: https://issues.apache.org/jira/browse/TS-3493 > Project: Traffic Server > Issue Type: Improvement > Components: HTTP/2 > Reporter: Leif Hedstrom > Assignee: Masakazu Kitajo > Labels: 5.3.0 > Fix For: 6.0.0 > > Attachments: TS-3493.patch > > > This is partially from the discussion on TS-3482: > Hmmm, chrome still show the window at 64K though :/ > Update: looking at the streams from https://www.google.com, I don't see much > different, other than the Google server also sending this frame: > [ 0.042] recv WINDOW_UPDATE frame <length=4, flags=0x00, stream_id=0> > (window_size_increment=983041) > I.e. > >>> 983041 + 65535 > 1048576 > which I don't see us doing. Maybe we have to send that frame explicitly as > well? Maybe this is a separate issue though? -- This message was sent by Atlassian JIRA (v6.3.4#6332)