Re: dont-revalidate Cache-Control header

Ben Maurer <ben.maurer@gmail.com> Tue, 14 July 2015 10:21 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 41BF81A9173 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 Jul 2015 03:21:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.011
X-Spam-Level:
X-Spam-Status: No, score=-7.011 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id p7CqHgMc8Uro for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 14 Jul 2015 03:21:36 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 795661A9172 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 14 Jul 2015 03:21:36 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ZExI7-0001cG-7C for ietf-http-wg-dist@listhub.w3.org; Tue, 14 Jul 2015 10:18:23 +0000
Resent-Date: Tue, 14 Jul 2015 10:18:23 +0000
Resent-Message-Id: <E1ZExI7-0001cG-7C@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <ben.maurer@gmail.com>) id 1ZExI3-0001bU-N9 for ietf-http-wg@listhub.w3.org; Tue, 14 Jul 2015 10:18:19 +0000
Received: from mail-lb0-f174.google.com ([209.85.217.174]) by lisa.w3.org with esmtps (TLS1.2:RSA_ARCFOUR_SHA1:128) (Exim 4.80) (envelope-from <ben.maurer@gmail.com>) id 1ZExI1-0001yh-B7 for ietf-http-wg@w3.org; Tue, 14 Jul 2015 10:18:18 +0000
Received: by lbbzr7 with SMTP id zr7so3290059lbb.1 for <ietf-http-wg@w3.org>; Tue, 14 Jul 2015 03:17:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=KHLnOj+Gs9gUb8FB85PBuxWTNi/5tlLRteqW5ZzkX4o=; b=mzQ5sDfB44JUWjhNvWDURrPjOdlaD83w7ZnSosXsU2TRP4H1d3sPOoad3FIr5cCot4 Pe3COUa/f7Fbk4I+dE23cJ9DGxZNvsu7wq0oWTvJX8Mgft52ehstsV6bPxPcT3t8Dt2E KR1P0mY6xHMv5VuHQ8PokTTh07txKxC84IIaXkoeUcvGmZLNTfux9bEpl4ODX9XGerwE UQEeFUQz0WVkYa1q3xp2iLxf3vox1Qe1hipUEUrQjxLbWz7JrqLPYKfkByiQOC9Fouvq 5Ia/KyfhWnMYPF1QBtnWzcoNf5NvcjB09lQIehkrFy7Bvir7MvyoLcA+JxNi+1nldDNh PA8A==
MIME-Version: 1.0
X-Received: by 10.152.19.35 with SMTP id b3mr36322856lae.92.1436869070408; Tue, 14 Jul 2015 03:17:50 -0700 (PDT)
Received: by 10.25.163.147 with HTTP; Tue, 14 Jul 2015 03:17:50 -0700 (PDT)
In-Reply-To: <CADLGQyCv5bjKswZJ=uyvbJLcgs96fvAOzs+2SNDkApBNLm3ZqA@mail.gmail.com>
References: <CADLGQyCv5bjKswZJ=uyvbJLcgs96fvAOzs+2SNDkApBNLm3ZqA@mail.gmail.com>
Date: Tue, 14 Jul 2015 11:17:50 +0100
Message-ID: <CABgOVaJCj0oAJ+xvy8NqC=qirVJyQ4gW_He+q+TKPXUv67jMPA@mail.gmail.com>
From: Ben Maurer <ben.maurer@gmail.com>
To: Bryan McQuade <bmcquade@google.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="089e01493fb287d1ac051ad32633"
Received-SPF: pass client-ip=209.85.217.174; envelope-from=ben.maurer@gmail.com; helo=mail-lb0-f174.google.com
X-W3C-Hub-Spam-Status: No, score=-5.6
X-W3C-Hub-Spam-Report: AWL=-0.909, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1ZExI1-0001yh-B7 ae5285ba892190b06b9336c4059fbb8a
X-Original-To: ietf-http-wg@w3.org
Subject: Re: dont-revalidate Cache-Control header
Archived-At: <http://www.w3.org/mid/CABgOVaJCj0oAJ+xvy8NqC=qirVJyQ4gW_He+q+TKPXUv67jMPA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29952
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Tue, Jul 14, 2015 at 12:49 AM, Bryan McQuade <bmcquade@google.com> wrote:

> Some history around page refresh->subresource reload browser behavior:
>
> HTTP/1.1 RFC (now deprecated):
> http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.9.4
> "14.9.4 Cache Revalidation and Reload Controls: Sometimes a user agent
> might want or need to insist that a cache revalidate its cache entry with
> the origin server ... End-to-end revalidation might be necessary if either
> the cache or the origin server has overestimated the expiration time of the
> cached response. End-to-end reload may be necessary if the cache entry has
> become corrupted for some reason."
>
> I take the above to suggest that the page refresh->reload subresource
> behavior was added to give users more certainty that refreshing a page
> would reload any corrupted or out of date resources. This seems like a fine
> default, but I agree with Ben that it'd be useful to allow web developers
> to opt out of this behavior.
>

For what it's worth, at least in our configuration reloading will do
absolutely nothing to fix cache corruption. The client will send us an
If-Modified-Since request, our servers will note that the resource has not
changed and we will send a 304. We've actually seen this in practice --
we've experienced issues where users somehow get corrupted resources (
https://code.google.com/p/chromium/issues/detail?id=161127). Refreshing
does *not* fix the issue, the users have to either clear cache or use a
ctrl+shift+r.

-b