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

Re: Support for gzip at the server #424 (Consensus Call)

From: Mark Nottingham <mnot@mnot.net>
Date: Mon, 28 Apr 2014 21:23:27 +1000
Cc: Matthew Kerwin <matthew@kerwin.net.au>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Message-Id: <A608FBED-F954-41EE-A6ED-C0CBC4789DF1@mnot.net>
To: "Julian F. Reschke" <julian.reschke@gmx.de>

On 28 Apr 2014, at 9:22 pm, Julian Reschke <julian.reschke@gmx.de> wrote:

> On 2014-04-28 12:45, Matthew Kerwin wrote:
>> ...
>> ​How does your non-browser client discover that the resource exists in
>> the first place, or can be POSTed or PUT to? That's the place to add
>> that it ​can handle zipped files. Whether that be in the linking
>> hypermedia, or offline API documentation, or a new link extension in a
>> Link header, etc.
>> ...
> Yes, many ways to do that. But there should be a single way, so that middleware can do it automatically.

As discussed, “middleware can do it automatically” and content-encoding don’t mix so well...

Mark Nottingham   http://www.mnot.net/
Received on Monday, 28 April 2014 11:23:53 UTC

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