Re: "Timeout" request header to tell server to wait for resource to become available
Brendan Long <self@brendanlong.com> Wed, 01 April 2015 15:11 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 32F171ACD96 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 1 Apr 2015 08:11:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.012
X-Spam-Level:
X-Spam-Status: No, score=-7.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 pqPEEFcjYsQw for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 1 Apr 2015 08:11:33 -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 E20881ACD93 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 1 Apr 2015 08:11:32 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1YdKFQ-00027k-St for ietf-http-wg-dist@listhub.w3.org; Wed, 01 Apr 2015 15:08:04 +0000
Resent-Date: Wed, 01 Apr 2015 15:08:04 +0000
Resent-Message-Id: <E1YdKFQ-00027k-St@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.80) (envelope-from <self@brendanlong.com>) id 1YdKFP-000276-Uz for ietf-http-wg@listhub.w3.org; Wed, 01 Apr 2015 15:08:03 +0000
Received: from li799-54.members.linode.com ([104.200.21.54] helo=brendanlong.com) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <self@brendanlong.com>) id 1YdKFL-00044N-CO for ietf-http-wg@w3.org; Wed, 01 Apr 2015 15:08:03 +0000
Received: by brendanlong.com (Postfix, from userid 1002) id C71FE50037; Wed, 1 Apr 2015 10:07:36 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brendanlong.com; s=default; t=1427900856; bh=LEAF6niywh4ngngw6n8EZZKy4VRkK4oDKztjWXxlgJ4=; h=Date:From:To:Subject:References:In-Reply-To; b=YQN5e7kg1eNvL9U9DlANpdM3SEdN9XlKCkwg+0d9IOAdyKsNizArM/ko2/nA07yGg 8GnQZIMzf1UnpKt6QGU4Wt4B5Jj7rq30pb494s8dzOq8byToUil/KSH5gfDWL2t3wg JciIDzugmzqfBgfNiP0wkmsnYqU8pOJacT+mW1S0=
Received: from [192.168.1.150] (96-42-255-30.dhcp.roch.mn.charter.com [96.42.255.30]) by brendanlong.com (Postfix) with ESMTPSA id 25A5E50036 for <ietf-http-wg@w3.org>; Wed, 1 Apr 2015 10:07:36 -0500 (CDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brendanlong.com; s=default; t=1427900856; bh=LEAF6niywh4ngngw6n8EZZKy4VRkK4oDKztjWXxlgJ4=; h=Date:From:To:Subject:References:In-Reply-To; b=YQN5e7kg1eNvL9U9DlANpdM3SEdN9XlKCkwg+0d9IOAdyKsNizArM/ko2/nA07yGg 8GnQZIMzf1UnpKt6QGU4Wt4B5Jj7rq30pb494s8dzOq8byToUil/KSH5gfDWL2t3wg JciIDzugmzqfBgfNiP0wkmsnYqU8pOJacT+mW1S0=
Message-ID: <551C09B7.6050604@brendanlong.com>
Date: Wed, 01 Apr 2015 10:07:35 -0500
From: Brendan Long <self@brendanlong.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: ietf-http-wg@w3.org
References: <5515F653.6080506@brendanlong.com> <200FC758-90CD-4F7B-88C4-DEAC3B7B5BB7@mnot.net>
In-Reply-To: <200FC758-90CD-4F7B-88C4-DEAC3B7B5BB7@mnot.net>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=104.200.21.54; envelope-from=self@brendanlong.com; helo=brendanlong.com
X-W3C-Hub-Spam-Status: No, score=-4.9
X-W3C-Hub-Spam-Report: AWL=-1.808, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1YdKFL-00044N-CO 1392d4cba8dda1273740fde11ebebfe5
X-Original-To: ietf-http-wg@w3.org
Subject: Re: "Timeout" request header to tell server to wait for resource to become available
Archived-At: <http://www.w3.org/mid/551C09B7.6050604@brendanlong.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/29181
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 03/31/2015 08:02 PM, Mark Nottingham wrote: > I guess I’m wondering why this needs to be coordinated between the client and server; couldn’t the DASH server just pause before determining that it really is a 404? > > I.e., are there other clients that need to know it’s a 404 right away? For the 404 case it's probably fine for the server to wait a little while, as long as it returns something before the connection times out (around a minute seems to be safe?). For the etag case, it would cause serious responsiveness problems for clients that do caching correctly but don't expect this behavior.
- "Timeout" request header to tell server to wait f… Brendan Long
- Re: "Timeout" request header to tell server to wa… Julian Reschke
- Re: "Timeout" request header to tell server to wa… Mark Nottingham
- Re: "Timeout" request header to tell server to wa… Brendan Long