[
https://issues.apache.org/jira/browse/TS-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14394428#comment-14394428
]
Leif Hedstrom commented on TS-3482:
-----------------------------------
Actually, it seems to work, not sure why Chrome shows me the old value (does it
cache it?) I see now
{code}
[ 0.039] recv SETTINGS frame <length=36, flags=0x00, stream_id=0>
(niv=6)
[SETTINGS_HEADER_TABLE_SIZE(0x01):4096]
[SETTINGS_ENABLE_PUSH(0x02):0]
[SETTINGS_MAX_CONCURRENT_STREAMS(0x03):66]
[SETTINGS_INITIAL_WINDOW_SIZE(0x04):123456]
[SETTINGS_MAX_FRAME_SIZE(0x05):16384]
[SETTINGS_MAX_HEADER_LIST_SIZE(0x06):4294967295]
{code}
That's with my settings of
CONFIG proxy.config.http2.max_concurrent_streams_in INT 66
CONFIG proxy.config.http2.initial_window_size_in INT 123456
I hope to land this patch for the configs soon.
> 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)
