[
https://issues.apache.org/jira/browse/TS-3493?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14395584#comment-14395584
]
Masakazu Kitajo commented on TS-3493:
-------------------------------------
It seems so. We have to send the WINDOW_UPDATE frame.
https://tools.ietf.org/html/draft-ietf-httpbis-http2-17#section-6.9.2
{quote}
Prior to receiving a SETTINGS frame that sets a value for
SETTINGS_INITIAL_WINDOW_SIZE, an endpoint can only use the default
initial window size when sending flow controlled frames. Similarly,
the connection flow control window is set to the default initial
window size until a WINDOW_UPDATE frame is received.
{quote}
> 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
> Fix For: 6.0.0
>
>
> 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)
