W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014

Error behevior of receiving PUSH_PROMISE when SETTINGS_ENABLE_PUSH is 0

From: Shigeki Ohtsu <ohtsu@iij.ad.jp>
Date: Thu, 09 Jan 2014 10:44:32 +0900
Message-ID: <52CDFF00.9050305@iij.ad.jp>
To: HTTP Working Group <ietf-http-wg@w3.org>
Hi,

There is no description about the behavior of receiving PUSH_PUROMISE when
SETTINGS_ENABLE_PUSH is 0.

As the other errors caused by PUSH_PROMISE, MUST the receiver treat it as
 a connection error of type PROTOCOL_ERROR?

The difference between two cases in receiving PUSH_PROMISE when
SETTINGS_MAX_CONCURRENT_STREAMS is 0 and when SETTINGS_ENABLE_PUSH is 0 is
that the former accepts PUSH_PROMISE whereas the latter does not.
Is this correct?

And I also found no description of the case when a server receive PUSH_PROMISE.
It should be also treated as a connection error. Right?

Regards,
Received on Thursday, 9 January 2014 01:45:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC