UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.91 Safari/537.36
Example URL:
Steps to reproduce the problem:
Use QUIC v40.
What is the expected behavior?
What went wrong?
QUIC v40 is supposed to implement the IETF format for RST_STREAM, ACK and STREAM frames.
Chrome currently writes the Data Length as first in the STREAM_FRAME in https://cs.chromium.org/chromium/src/net/quic/core/quic_framer.cc?q=quic_framer&sq=package:chromium&l=1995. According to the IETF draft (https://quicwg.github.io/base-drafts/draft-ietf-quic-transport.html#rfc.section.8.14), it should be written after the Offset.
Did this work before? No
Chrome version: 61.0.3163.91 Channel: canary
OS Version: OS X 10.12.6
Flash Version:
The issue seems to be out of TE-scope as it is related to QUIC. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.
Thanks...!!
Comment 1 by mmenke@chromium.org
, Sep 20 2017