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: Matthew Kerwin <matthew@kerwin.net.au>
Date: Mon, 28 Apr 2014 21:01:45 +1000
Message-ID: <CACweHNDz_2F9qGkWCjCk183qohTZS10zSjsZO2LCGj9gM82ZDg@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Apologies if I'm drifting off topic at all.


​On 28 April 2014 20:45, Mark Nottingham <mnot@mnot.net> wrote:

>
> On 28 Apr 2014, at 8:09 pm, Matthew Kerwin <matthew@kerwin.net.au> wrote:
>
> >
> > ​<form action="/rsrc-that-accepts-gzip" method="POST"><input type="file"
> name="f"></form>
> > ​<p>Select a file to upload (gzip files will be automatically
> extracted)</p>
>
> True - but I was thinking of something like
>
> <form action=“/foo” method=“POST” content-encoding=“gzip”>…</form>
>
>

That introduces a UI/UX problem; ​does a browser present the gzip support
to the human? And if so, how does the human choose between: here's a file
which is already gzipped / here's a file which you can gzip for me* /
here's a file, don't gzip it?

* urgh, and is this any better than dynamic C-E in responses?

-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/
Received on Monday, 28 April 2014 11:02:13 UTC

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