Re: dont-revalidate Cache-Control header

Ben Maurer <ben.maurer@gmail.com> Fri, 17 July 2015 09:27 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 3B0D41B3202 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 17 Jul 2015 02:27:14 -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 q-tZEereSlZf for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 17 Jul 2015 02:27:12 -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 D848C1B31F1 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 17 Jul 2015 02:27:12 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1ZG1rs-00055c-Dc for ietf-http-wg-dist@listhub.w3.org; Fri, 17 Jul 2015 09:23:44 +0000
Resent-Date: Fri, 17 Jul 2015 09:23:44 +0000
Resent-Message-Id: <E1ZG1rs-00055c-Dc@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) 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 1ZG1rl-00054h-Qa for ietf-http-wg@listhub.w3.org; Fri, 17 Jul 2015 09:23:37 +0000
Received: from mail-la0-f43.google.com ([209.85.215.43]) by maggie.w3.org with esmtps (TLS1.2:RSA_ARCFOUR_SHA1:128) (Exim 4.80) (envelope-from <ben.maurer@gmail.com>) id 1ZG1rk-0005rH-4g for ietf-http-wg@w3.org; Fri, 17 Jul 2015 09:23:37 +0000
Received: by lagx9 with SMTP id x9so57788125lag.1 for <ietf-http-wg@w3.org>; Fri, 17 Jul 2015 02:23:09 -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=tDnVL20ALC1kLo9gDQdF+p97thGfYOQ38R34GiCUB8Y=; b=A5IGjO/SWbtONVywijBc/pSyI/cGkOxfmgTCXmncB+zsz/ujZvNTW7A/9Qu3/7F3Bt FCsfQxR6cN4FQjbRDkC/IWAZKlNPYoJlhhKlKALZTz2ikda7Ua8gq0psNbjTWwN99cum GvOl2LuC7i4KdUSx6MVMd1eDggCxU7pN6aMyo7hE3jEuSECix9mTBBXXXk+t9WxPbcxH hAOfd+s8UwYB1OZItWqIT68W21E/owyncr+dTGCnV3UJIct8RKIyuakqfo+OuGs/N2Km YNKQvNkgMgEYv7OrWCCSnFlh5gd5aVq3xf87RpB9bEzRH5Qw8bKYIDYVyHi3a7Jh/rkO GcVA==
MIME-Version: 1.0
X-Received: by 10.112.219.70 with SMTP id pm6mr13283282lbc.41.1437124989600; Fri, 17 Jul 2015 02:23:09 -0700 (PDT)
Received: by 10.25.163.147 with HTTP; Fri, 17 Jul 2015 02:23:09 -0700 (PDT)
In-Reply-To: <CABkgnnWG9mSg=pCT91tVfEEs1TCxHVnNWRopsPTr+eC4K4Vewg@mail.gmail.com>
References: <CABgOVaLHBb4zcgvO4NUUmAzUjNkocBGYY3atFA9iuYyoLaLQsA@mail.gmail.com> <559F9E90.4020801@treenet.co.nz> <CABgOVaLG6QZyjqk2AGYupShST_u3ty9BpxUcPX+_yMEC1hyHAQ@mail.gmail.com> <961203FE-7E54-410F-923E-71C04914CD2E@mnot.net> <CABgOVaJxntEyT0v4GvWm0Qi9jbUPEnzxJgg4KyQSM1T_gN1mjQ@mail.gmail.com> <16407353-5C34-42E8-81A6-E0027EC3A0D0@mnot.net> <CABgOVa+C48yYp-ZkawY+Ho6pXONa_UfB0MVt_2+d0ejyESu2Pw@mail.gmail.com> <54973543-2406-4188-8DCD-AE3C85ACB76A@mnot.net> <CABgOVa+CrJ0qBGN-nBYZ2qpJo8X+wkYY-zYAqM6MjTom1QT+Bw@mail.gmail.com> <55A7A4F9.1010500@treenet.co.nz> <CABgOVaLnpnmd7JvY6O=tXXboVuvCCn-p1KLzu8wKVkg-yon79w@mail.gmail.com> <CAMSE37vmBJYkiC+c5+aMqWUvLtY4zOHDbhEJkm=K+=KbTyOO2A@mail.gmail.com> <CABkgnnXNAZdXUx_htq2owyP2CtyM-ERzZdbxM8WGWLrCeNQOaQ@mail.gmail.com> <CAMSE37v6qXzNquAqGPaHgVJYwfGeC+uE1hurc7g4wvoL1nvgkA@mail.gmail.com> <CABkgnnX3OMJ2=5AQcYHB9XeN0TEo0OTrcRmrpBujrqCNwnjOag@mail.gmail.com> <CAMSE37uwbLokWApCUMtj5G9zW4p5RzY63XOx-+VeiRdouw3-SA@mail.gmail.com> <CABkgnnWG9mSg=pCT91tVfEEs1TCxHVnNWRopsPTr+eC4K4Vewg@mail.gmail.com>
Date: Fri, 17 Jul 2015 10:23:09 +0100
Message-ID: <CABgOVaKWKjVcbKpMj-KtWzO1O+VVSDKSH80t3pisoPAM8mt+7A@mail.gmail.com>
From: Ben Maurer <ben.maurer@gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Guille -bisho- <bishillo@gmail.com>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="001a11c3ccd880cac4051b0ebc63"
Received-SPF: pass client-ip=209.85.215.43; envelope-from=ben.maurer@gmail.com; helo=mail-la0-f43.google.com
X-W3C-Hub-Spam-Status: No, score=-5.6
X-W3C-Hub-Spam-Report: AWL=-0.901, 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: maggie.w3.org 1ZG1rk-0005rH-4g 97402528a51583109362f07eb347c571
X-Original-To: ietf-http-wg@w3.org
Subject: Re: dont-revalidate Cache-Control header
Archived-At: <http://www.w3.org/mid/CABgOVaKWKjVcbKpMj-KtWzO1O+VVSDKSH80t3pisoPAM8mt+7A@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29983
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 Thu, Jul 16, 2015 at 9:07 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:
>
> Like I said, you can implement your proposed solution today, without
> writing any standards.  Sure, only Chrome supports it right now, but
> that's a whole lot more of the web than none of it.
>

Using unique URIs to define resources is a common behavior to many sites
and is widely recommended in blogs/books/etc. It seems worth creating a
standard way to implement this recommendation that is far simpler than a
service worker.

Shift-reload is a tool we provide our users to get around this class of
> problem.


This draft does not suggest altering the behavior of shift-reload.
Shift-reload should continue to be an absolute refresh of the site -- for
example I believe in Chrome shift-reload even ignores service workers. In
future drafts it may be worth being more clear about this behavior.

-b