W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2016

Re: Submitted new I-D: Cache Digests for HTTP/2

From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 3 Feb 2016 15:19:14 +1100
Message-ID: <CABkgnnU=BEPC=2X1f+DKDd11CrEG1awDG=j+J-Ha3B-mTPxfvA@mail.gmail.com>
To: Amos Jeffries <squid3@treenet.co.nz>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On 3 February 2016 at 07:26, Amos Jeffries <squid3@treenet.co.nz> wrote:
> That is because PUSH by itself cannot do conditional requests. Consider
> it to be the equivalent for a non-conditional request that always gets
> the 200 status response with full new object and new expiry details.

This isn't strictly true.  You can server push a conditional request,
and in fact it can be advantageous to do so.

Of course, the server doesn't always know enough about a client to
make the *right* conditional request.
Received on Wednesday, 3 February 2016 04:19:45 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 22 March 2016 12:47:11 UTC