Re: Recursive HTTP/2 Push

>
> The spec is clear the server must not send. In general that doesn't create
> a requirement on the peer to throw a protocol_error when receiving.
>

In this case the spec does have an explicit requirement (section 5.1) that
a client in the "reserved (remote)" state throw a p_e.

"Receiving any type of frame other than HEADERS, RS_STREAM, or PRIORITY on
a stream in this state MUST be treated as a connection error (Section
5.4.1) of type PROTOCOL_ERROR."