search

httpwg / http2-spec

Working copy of the HTTP/2 Specification
https://httpwg.org/
3.72k stars 565 forks source link

Gzip transfer encoding #345

Closed const closed 10 years ago

const commented 10 years ago

Looking at GZip format there is the following specified in http://tools.ietf.org/html/rfc1952#page-5

   2.2. File format

      A gzip file consists of a series of "members" (compressed data
      sets).  The format of each member is specified in the following
      section.  The members simply appear one after another in the file,
      with no additional information before, between, or after them.

In the draft draft-ietf-httpbis-p1-messaging-25.xml the following is said.

<section title="Gzip Coding" anchor="gzip.coding">
<iref item="gzip (Coding Format)"/>
<t>
   The "gzip" coding is an LZ77 coding with a 32 bit CRC that is commonly
   produced by the gzip file compression program <xref target="RFC1952"/>.
   A recipient &SHOULD; consider "x-gzip" to be equivalent to "gzip".
</t>
</section>

It is not clear whether multiple members are allowed for gzip or not and how they should be treated if they are allowed. I think that only one member in the file should be used for transfrer encoding "gzip". The same should be defined for content encoding. I doubt that anyone supports multi-member gzip format on webservers.

reschke commented 10 years ago

Please send feedback related to the 1.1 documents to the HTTPbis WG mailing list (as indicated in the document's boilerplate).