Subject: [httpwg/http-extensions] change frame type of origin to 0xc to avoid conflict (#323)

From: HTTP issue updates <[email-masked]>
Date: Mon, 10 Apr 2017 18:05:06 -0700

While testing firefox's implementation of this draft Vlad determined that some versions of Chrome throw PROTOCOL_ERROR and close the connection if it receives a type 0xB frame with a non zero length on stream 0.

Other frame type numbers, such as 0xC do not seem to have that problem.

testing indicates this is fixed in version 59 and is a problem previous to that. (57 is in release as I write this).

presumably this is related to historical code around BLOCKED which was proposed to use 0xB.

Prudence says to just use a different code point for the moment.
You can view, comment on, or merge this pull request online at:

  https://github.com/httpwg/http-extensions/pull/323

-- Commit Summary --

  * change frame type of origin to 0xc to avoid conflict

-- File Changes --

    M draft-ietf-httpbis-origin-frame.md (4)

-- Patch Links --

https://github.com/httpwg/http-extensions/pull/323.patch
https://github.com/httpwg/http-extensions/pull/323.diff

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/httpwg/http-extensions/pull/323