[
https://issues.apache.org/jira/browse/TS-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14481403#comment-14481403
]
ASF subversion and git services commented on TS-3493:
-----------------------------------------------------
Commit 26fe75924b6e926115b6b043641c7e4adc1b7249 in trafficserver's branch
refs/heads/5.3.x from [~zwoop]
[ https://git-wip-us.apache.org/repos/asf?p=trafficserver.git;h=26fe759 ]
Added TS-3493
(cherry picked from commit ede0f007d9d6058da059c14e4807ef9e1e7e6b37)
Conflicts:
CHANGES
> 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
> 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)
