Uploaded image for project: 'Traffic Server'
  1. Traffic Server
  2. TS-3481

Changing HTTP2_INITIAL_WINDOW_SIZE does not reflect in e.g. Chrome conn status

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: HTTP/2
    • Labels:
      None

      Description

      If I change the hardcoded value for HTTP2_INITIAL_WINDOW_SIZE (default 64k) to e.g. 1M, the connection inspection plugin for Chrome still shows the 64k default. I don't know if it's actually using the new (1M) size, it looks like the settings frame should include this new value. However, chrome does not seem to think so.

      Changing HTTP2_MAX_CONCURRENT_STREAMS seems to work fine.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                rokubo Ryo Okubo
                Reporter:
                zwoop Leif Hedstrom
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: