RE: "Upgrade: h2c"

Hi Mark & Willy-

Thanks for the information and link.  I didn't realize that Section 3.2 was following the guidelines in RFC 7230.

I still think it would be useful to allow the client to _speculatively_ include "pipelined" h2c requests in a HTTP2-Frames base-64 encoded header which would include a required settings frame and 0 or more optional HEADERS frames: SETTINGS HEADERS*

What do you think?

I'm also curious what the _Microsoft_ guys think since they are apparently the only browser that will support "Upgrade" to h2c.


This email message is intended only for the use of the named recipient. Information contained in this email message and its attachments may be privileged, confidential and protected from disclosure. If you are not the intended recipient, please do not read, copy, use or disclose this communication to others. Also please notify the sender by replying to this message and then delete it from your system.

Received on Wednesday, 16 July 2014 10:26:18 UTC