[
https://issues.apache.org/jira/browse/TS-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394874#comment-14394874
]
Leif Hedstrom edited comment on TS-3482 at 4/3/15 6:50 PM:
-----------------------------------------------------------
Hmmm, chrome still shows 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:
{code}
[ 0.042] recv WINDOW_UPDATE frame <length=4, flags=0x00, stream_id=0>
(window_size_increment=983041)
{code}
I.e.
>>> 983041 + 65535
1048576
which I don't see us doing. Maybe we have to send that frame explicitly as well?
was (Author: zwoop):
Hmmm, chrome still shows 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:
{code}
[ 0.042] recv WINDOW_UPDATE frame <length=4, flags=0x00, stream_id=0>
(window_size_increment=983041)
{code}
which I don't see us doing. Maybe we have to send that frame explicitly as well?
> SETTINGS frame contains not only valid parameters
> -------------------------------------------------
>
> Key: TS-3482
> URL: https://issues.apache.org/jira/browse/TS-3482
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP/2
> Reporter: Masakazu Kitajo
> Fix For: 6.0.0
>
> Attachments: fix_settings_frame.patch
>
>
> The first SETTINGS frame sent by TS contains not only valid parameters but
> also dead beef.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
