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

hpack table size 0

From: <K.Morgan@iaea.org>
Date: Mon, 30 Jun 2014 11:58:09 +0000
To: <ietf-http-wg@w3.org>
Message-ID: <0356EBBE092D394F9291DA01E8D28EC20118700AE6@sem002pd>
It's been mentioned previously that resource-constrained implementations may set the table size to 0 (i.e. SETTINGS_HEADER_TABLE_SIZE).

Assume a server has table size 0... Questions:

1. The client's first request will likely include entries that are "Literal Header Field with Incremental Indexing".  I assume it is OK for the server to process a request with this type of literal even though the server won't be adding to its 0-size table?  Am I missing something?

2. If the client is sending multiple requests right after the connection is opened, each request after the first will likely include entries that reference the table (i.e. "Indexed Header Field Representation").  What is an endpoint supposed to do if the peer references something not in its table?  REFUSED_STREAM?  What mechanism should be used to tell the peer to retry?

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 Monday, 30 June 2014 11:58:40 UTC

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