Indexing new entry with a size greater than SETTINGS_HEADER_TABLE_SIZE

I suggest that indexing new entry with a size greater than


SETTINGS_HEADER_TABLE_SIZE MUST NOT be done.



Here is the current wording:


"""

   The addition of a new entry with a size greater than the
   SETTINGS_HEADER_TABLE_SIZE limit causes all the entries from the
   header table to be dropped and the new entry not to be added to the
   header table.  The replacement of an existing entry with a new entry
   with a size greater than the SETTINGS_HEADER_TABLE_SIZE has the same
   consequences.

"""

The reason is that it just brings negative effect to the compressor; it
clears all entries in
the header table, which would have been utilized to reduce bytes on the
wire, and yet
the entry itself disappears into the void. Just no gains at all.
Trying to add the entry to the header table knowing it cannot is just a bug
to me.

It is easy for the encoder to check the required space for the new entry is
strictly larger
than SETTINGS_HEADER_TABLE_SIZE. And if so, just encode it in literal
without
indexing. For the decoder, it has to check the required room for new entry
nonetheless
and just return error if the size is exceeded the limit.

Best regards,
Tatsuhiro Tsujikawa