Re: Server Push Error Codes
Martin Thomson <martin.thomson@gmail.com> Wed, 24 August 2016 05:35 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C262512D556 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 23 Aug 2016 22:35:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.569
X-Spam-Level:
X-Spam-Status: No, score=-7.569 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 kQgRp7k2wcoj for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 23 Aug 2016 22:35:48 -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 EBB7712D532 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 23 Aug 2016 22:35:47 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bcQmJ-0003Wz-0V for ietf-http-wg-dist@listhub.w3.org; Wed, 24 Aug 2016 05:31:07 +0000
Resent-Date: Wed, 24 Aug 2016 05:31:07 +0000
Resent-Message-Id: <E1bcQmJ-0003Wz-0V@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 <martin.thomson@gmail.com>) id 1bcQmA-0003WI-Qj for ietf-http-wg@listhub.w3.org; Wed, 24 Aug 2016 05:30:58 +0000
Received: from mail-qk0-f176.google.com ([209.85.220.176]) by lisa.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <martin.thomson@gmail.com>) id 1bcQm6-0002tc-OF for ietf-http-wg@w3.org; Wed, 24 Aug 2016 05:30:57 +0000
Received: by mail-qk0-f176.google.com with SMTP id z190so5563103qkc.0 for <ietf-http-wg@w3.org>; Tue, 23 Aug 2016 22:30:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tiXLF1Hgx4hVAGqgU6BaLSErMLqonOxnnlZdZsQtWvc=; b=E+ZG8cXY6dCP5O3/ia46+wmGuj+CXjVo5aSGo4M2S9M80F/v6+ofQVZdBKujKCuDWt 0bojJjFF+H1FgfEpPP4b6WsdmGOBeKGdCBqCO5GBxeLE9Xly8fbadVyttMpMqD89CAz/ +gJRsXgd+c9gx5Kni86GGzsCnvpIrxtTK3jkjLYBE6lZR6Aov5oockZTxIEjkkxW2GnB Vo7OWjs43vaMmvnNmOE+zAQcx+/BEDXEXSEprJ8HUzPoymKwySZshcXMW7SPSgP4BHc8 kiMBUubxWIaYPWIgxNc+9lp0RK+wnUvcQCLaYzv1iuWyvyPd7/T1mABbqNEj8QuKiHs+ YB4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tiXLF1Hgx4hVAGqgU6BaLSErMLqonOxnnlZdZsQtWvc=; b=cydWQIBkEetT7fZXqgHisojM9EPzTMjcJZn+LU2IZHtSUmwr69xretfnqRg7PragCO VLp1r9LpftoBmWJ1o1VlG5YM3ca9WabwlQDvzZL9lqiKxVutUT7yFJxPjLW1+AITf9wt Y5pUT7csYtWjPQq0hoNi9BLqd/sgFlQW0NlBDOubm8M4KZq8Wzko6jNNQxFdJJYFDmGF +Gh/p8fiqCp400qhsxeA3IozG/RJ1ZN+ZA1IlOPjUWVZ8px3gLBpHz/O8Cy5y4ZxmWh+ kruZe12NIcrBi2RXTdfWdPXzM8jBolyL2+YLGpDyC6EBg5bXzoiHoevwCq2PMPFLjKvV BRNg==
X-Gm-Message-State: AE9vXwMmHIjlktlso8Ym0SIa5CelZoZwFm271X6KfBlyXA2fdVdVFU73a5q6gHs+x5ePv4w4OBR1RIPDq61Ypw==
X-Received: by 10.55.165.65 with SMTP id o62mr1388875qke.282.1472016628739; Tue, 23 Aug 2016 22:30:28 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.22.146 with HTTP; Tue, 23 Aug 2016 22:30:28 -0700 (PDT)
In-Reply-To: <077CD10C-E189-47B0-A221-3EA270B2B55D@mnot.net>
References: <077CD10C-E189-47B0-A221-3EA270B2B55D@mnot.net>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 24 Aug 2016 15:30:28 +1000
Message-ID: <CABkgnnVE8OBy_oxbw86ZNf0AHnywmTPAgEFNm8w9sSu-Q0FXKw@mail.gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.220.176; envelope-from=martin.thomson@gmail.com; helo=mail-qk0-f176.google.com
X-W3C-Hub-Spam-Status: No, score=-7.9
X-W3C-Hub-Spam-Report: AWL=1.832, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1bcQm6-0002tc-OF 0afc8024142de4916a67e811ce05f841
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Server Push Error Codes
Archived-At: <http://www.w3.org/mid/CABkgnnVE8OBy_oxbw86ZNf0AHnywmTPAgEFNm8w9sSu-Q0FXKw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32343
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>
These seem mostly reasonable. On 24 August 2016 at 14:26, Mark Nottingham <mnot@mnot.net> wrote: > # PUSH_UNAUTHORITATIVE We are looking to provide solutions that make this unnecessary (absent outright errors), but I think that it's a good code to have. > # PUSH_CONTENT_ENCODING_NOT_SUPPORTED This seems like it could be overly specific. PUSH_NOT_ACCEPTABLE might be used to cover Accept as well as Accept-Encoding. Unless you want both. For content-encoding, it seems unlikely that the server will get this wrong. The server might reasonably assume that the value for Accept-Encoding is constant and it will usually be right. If not, read on. For Accept, a server might get it wrong, but it is probably the case that the right machinery for determining whether a response is acceptable isn't engaged when the push arrives. That usually requires a bunch of other context. The same applies if Accept-Encoding isn't constant.
- Server Push Error Codes Mark Nottingham
- Re: Server Push Error Codes Martin Thomson
- Re: Server Push Error Codes Mark Nottingham
- Re: Server Push Error Codes Emily Shepherd
- Re: Server Push Error Codes Martin Thomson
- Re: Server Push Error Codes Patrick McManus
- RE: Server Push Error Codes Mike Bishop