Re: draft-ietf-httpbis-http2-latest, "8.2.1 Push Requests"

In addition to the "not known to be safe" thing, this highlights
something that isn't perfectly clear here.  The PROTOCOL_ERROR needs
to be on the promised stream, otherwise servers could be effectively
prevented from using new safe methods for push promise.

On 13 January 2015 at 07:22, Julian Reschke <> wrote:
> <>:
> "If a client receives a PUSH_PROMISE that does not include a complete and
> valid set of header fields, or the :method header field identifies a method
> that is not safe, it MUST respond with a stream error (Section 5.4.2) of
> New safe methods can be defined. Does this mean that the client needs to
> respond with a stream error for methods *not known to be safe*?
> Best regards, Julian

Received on Sunday, 18 January 2015 21:08:31 UTC