Re: [quicwg/base-drafts] Push and Cache Interaction (#3530)

"Roy T. Fielding" <notifications@github.com> Thu, 19 March 2020 17:15 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C4103A09F0 for <quic-issues@ietfa.amsl.com>; Thu, 19 Mar 2020 10:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.482
X-Spam-Level:
X-Spam-Status: No, score=-1.482 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
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 0JNWWHYWCdmL for <quic-issues@ietfa.amsl.com>; Thu, 19 Mar 2020 10:15:29 -0700 (PDT)
Received: from out-25.smtp.github.com (out-25.smtp.github.com [192.30.252.208]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6608D3A09E2 for <quic-issues@ietf.org>; Thu, 19 Mar 2020 10:15:29 -0700 (PDT)
Date: Thu, 19 Mar 2020 10:15:28 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1584638128; bh=N3h1jnuAjj6idn8Ng7olIMCImrm6BwNqowMC43sd8dU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EXDflOssz42E8y/8U/V0wxZYdytmxCgkl00lqwLikkulPNNWm+dHtDvJDNHb8fpTC BrfsTpHqugwSGaPiw8Ez+MDwr2k55HT9Syq2R4AH5CVU3GtPgVpv7azd5M3yCZKt53 xFEDwOegZpXYn5Goi7fYPcMYmxmBzFYCrvu1+t+8=
From: "Roy T. Fielding" <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZPSEQYLDMCUHHMDWF4P6E3BEVBNHHCFTFZFI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3530/601306624@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3530@github.com>
References: <quicwg/base-drafts/issues/3530@github.com>
Subject: Re: [quicwg/base-drafts] Push and Cache Interaction (#3530)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e73a8b039998_20733fdb10ecd9681076eb"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: royfielding
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/R1fTgtXUzk09Y1-tMFK0nnfMpLU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Mar 2020 17:15:32 -0000

My comment was intended to be editorial for QUIC, but it is also critical to understand from an implementation perspective (regardless of protocol).

When a browser makes a request and receives a 2xx response, that response is not "part of the cache". It is part of the working state (hypertext workspace) for the user agent (windows/tabs/history). The response may also be cached, but the working state is not subject to cache controls or freshness. The same should be true for push or it won't be usable for non-cached session-specific content.

I don't need QUIC to redefine that. It's actually something that should be defined by user agents (Fetch). What I need is for the HTTP/3 text to be consistent with the existing distinction between the working state of a user agent and the terminology for a cache. They are distinct on purpose. We should probably reinforce that in http-core as well, beyond the brief section in Caching.

I'd prefer that we keep this open (editorial) until I get a chance to review the next draft version.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/3530#issuecomment-601306624