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

Design Issue: GZIP flag on DATA Frames

From: James M Snell <jasnell@gmail.com>
Date: Tue, 21 May 2013 09:21:27 -0700
Message-ID: <CABP7Rbfb92Vxrmxj6fKdt+jpO_Qknq8FRjsu5GZW=17uoi4OFg@mail.gmail.com>
To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>

Currently the spec includes a requirement that all user-agents MUST
support gzip.. specifically:

  User-agents MUST support gzip compression.
  Regardless of the Accept-Encoding sent by
  the user-agent, the server may always send
  content encoded with gzip or deflate encoding.

If we're going to include this requirement, it makes more sense to do
this at the framing layer rather than the HTTP semantic layer. We can
do so easily by defining a GZIP flag on the DATA frame type. If set,
the payload of the DATA frame is compressed.

Doing so largely eliminates the need for the
accept-/transfer-/content-encoding mechanisms at the http semantic
Received on Tuesday, 21 May 2013 16:22:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:13 UTC