- From: Ilari Liusvaara <ilariliusvaara@welho.com>
- Date: Sat, 12 Oct 2024 10:05:08 +0300
- To: ietf-http-wg@w3.org
On Fri, Oct 11, 2024 at 09:46:20PM -0400, Josh Cohen wrote: > Ilari said: "For HTTP/2, that was one of the things removed in RFC9113 (the > original RFC7540 had that capability)." > > > That would be raining on the Symmetric HTTP parade (: However, I looked > through the RFCs and I didn't see that. RFC9113 still mentions even > numbered IDs for server initiated streams. I see a difference in the > SETTING param for ENABLE_PUSH, but it doesn't prohibit it. > > > Can you steer me towards where server initiated streams are prohibited? RFC9113 section 5.1. Stream States: idle: "If this stream is initiated by the server, as described in Section 5.1.1, then receiving a HEADERS frame MUST also be treated as a connection error (Section 5.4.1) of type PROTOCOL_ERROR." (Also, the transition list only mentions HEADERS in: "Sending a HEADERS frame as a client, or receiving a HEADERS frame as a server, causes the stream to become 'open'." Whereas the corresponding section in RFC7540 lacks the first text and the second text is not directional: "Sending or receiving a HEADERS frame causes the stream to become 'open'." -Ilari
Received on Saturday, 12 October 2024 07:05:15 UTC