Re: Protocols/APIs and redirects
Herbert van de Sompel <hvdsomp@gmail.com> Fri, 09 December 2011 17:45 UTC
Return-Path: <ietf-http-wg-request@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 D25EF21F88B6 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 9 Dec 2011 09:45:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.598
X-Spam-Level:
X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d35zp5Hio7VU for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 9 Dec 2011 09:45:55 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id D2A4321F87FC for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 9 Dec 2011 09:45:54 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.69) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1RZ4V8-0001v0-5b for ietf-http-wg-dist@listhub.w3.org; Fri, 09 Dec 2011 17:44:50 +0000
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.69) (envelope-from <hvdsomp@gmail.com>) id 1RZ4Uu-0001qi-Ex for ietf-http-wg@listhub.w3.org; Fri, 09 Dec 2011 17:44:36 +0000
Received: from mail-pz0-f43.google.com ([209.85.210.43]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <hvdsomp@gmail.com>) id 1RZ4Um-0007QP-9g for ietf-http-wg@w3.org; Fri, 09 Dec 2011 17:44:32 +0000
Received: by dadz13 with SMTP id z13so3823390dad.2 for <ietf-http-wg@w3.org>; Fri, 09 Dec 2011 09:44:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=9jcIr89+3j1c/32EIponD6WbY0ysF/+0sfN6OWaaxIQ=; b=x7rjJCao9usPSBvIWTViUotH0t+5qiwpCYcEoW59GIcgJJ8jkmrHYTraQsawYUpRXY x1STyCWGcg6epyq9yfmVkJj127Y3ZDABOUIUPDjyfkrXnwA3gSL7etVmoLJjOwE4//rQ BYUiikKkRrDH+foExHtCDXisJFlFEaxfHb9i8=
MIME-Version: 1.0
Received: by 10.68.74.227 with SMTP id x3mr7974797pbv.114.1323452642925; Fri, 09 Dec 2011 09:44:02 -0800 (PST)
Received: by 10.68.43.225 with HTTP; Fri, 9 Dec 2011 09:44:02 -0800 (PST)
In-Reply-To: <7BD18309-2771-47A2-ADB1-3319FB3C68C7@mnot.net>
References: <op.v52euanp64w2qv@annevk-macbookpro.local> <op.v52e7ubx64w2qv@annevk-macbookpro.local> <FC7A6CA0-107B-4373-BBDA-C31A5D9E431A@mnot.net> <op.v535r5iz64w2qv@annevk-macbookpro.local> <4EDF54BC.5090603@gmx.de> <op.v54k0gf864w2qv@annevk-macbookpro.local> <7BD18309-2771-47A2-ADB1-3319FB3C68C7@mnot.net>
Date: Fri, 09 Dec 2011 10:44:02 -0700
Message-ID: <CAOywMHfAEVSXbSEeCef6SUqaNJ1Lty30iuo98CWkk+qvQ2v7NA@mail.gmail.com>
From: Herbert van de Sompel <hvdsomp@gmail.com>
To: Mark Nottingham <mnot@mnot.net>
Cc: Anne van Kesteren <annevk@opera.com>, Julian Reschke <julian.reschke@gmx.de>, HTTP WG <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="f46d040f9c2aa89e4e04b3ac54cb"
Received-SPF: pass client-ip=209.85.210.43; envelope-from=hvdsomp@gmail.com; helo=mail-pz0-f43.google.com
X-W3C-Hub-Spam-Status: No, score=-2.7
X-W3C-Hub-Spam-Report: 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
X-W3C-Scan-Sig: lisa.w3.org 1RZ4Um-0007QP-9g ae08bb2bff449329f967ee17234a2add
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Protocols/APIs and redirects
Archived-At: <http://www.w3.org/mid/CAOywMHfAEVSXbSEeCef6SUqaNJ1Lty30iuo98CWkk+qvQ2v7NA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/11809
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>
Resent-Message-Id: <E1RZ4V8-0001v0-5b@frink.w3.org>
Resent-Date: Fri, 09 Dec 2011 17:44:50 +0000
Dear all, I hope that it's useful to share our experiences with redirects in the Memento "Time Travel for the Web" project [1] and the development of Memento clients such as the FireFox add-on MementoFox [2]: 1. Being able to intercept HTTP requests in the client at every step is critically important for us in order to be able to accurately navigate to prior versions of resources. Please imagine the following case: - 12 months ago, a given URI (R1) redirected to a particular image (I1). - Today, it redirects to a different image (I2). In order for a Memento client to be able to retrieve the image that was the end result of the redirect 12 months ago (I1), it must be able to intercept the first URI requested (R1) and start time traveling from there. Indeed, if not intercepting the first URI and hence following the redirect chain, the Memento client would end up at image I2, which was not the active resource 12 months ago. As it is important to be able to do this same interception for any HTTP request, automatically and unpreventably following links in XMLHttpRequest or any other context is very disruptive. 2. There is another issue regarding automatic following, which is possibly tangential to the current discussion, but we feel is worth bringing up. The Link Header RFC [3] allows target URIs to be associated in the HTTP headers with the responding resource. It would be very useful if users could set preferences to allow following these links, even if the response is not a 3XX status. In Memento clients, this would allow to e.g. follow a link to a TimeGate. Thank you for the consideration, Herbert Van de Sompel, Michael Nelson, Robert Sanderson [1] Memento: http://mementoweb.org/ ; Internet Draft: https://datatracker.ietf.org/doc/draft-vandesompel-memento/ [2] https://addons.mozilla.org/en-US/firefox/addon/mementofox/ [3]RFC5988: http://tools.ietf.org/html/rfc5988 -- Herbert Van de Sompel Digital Library Research & Prototyping Los Alamos National Laboratory, Research Library http://public.lanl.gov/herbertv/ ==
- Protocols/APIs and redirects Anne van Kesteren
- Re: Protocols/APIs and redirects Anne van Kesteren
- Re: Protocols/APIs and redirects Julian Reschke
- Re: Protocols/APIs and redirects Amos Jeffries
- Re: Protocols/APIs and redirects Julian Reschke
- Re: Protocols/APIs and redirects Roy T. Fielding
- Re: Protocols/APIs and redirects Mark Nottingham
- Re: Protocols/APIs and redirects Julian Reschke
- Re: Protocols/APIs and redirects Mark Nottingham
- issue 325: When are Location's semantics triggere… Julian Reschke
- Re: Protocols/APIs and redirects Anne van Kesteren
- Re: Protocols/APIs and redirects Julian Reschke
- Re: issue 325: When are Location's semantics trig… Willy Tarreau
- Re: issue 325: When are Location's semantics trig… Julian Reschke
- Re: Protocols/APIs and redirects Anne van Kesteren
- Re: Protocols/APIs and redirects Julian Reschke
- Re: issue 325: When are Location's semantics trig… Cameron Heavon-Jones
- Re: issue 325: When are Location's semantics trig… Julian Reschke
- Re: issue 325: When are Location's semantics trig… Cameron Heavon-Jones
- Re: Protocols/APIs and redirects Mark Nottingham
- Re: Protocols/APIs and redirects Anne van Kesteren
- Re: Protocols/APIs and redirects Mark Nottingham
- Re: Protocols/APIs and redirects Herbert van de Sompel
- Re: issue 325: When are Location's semantics trig… Mark Nottingham
- Re: issue 325: When are Location's semantics trig… Willy Tarreau
- Re: issue 325: When are Location's semantics trig… Mark Nottingham
- Re: issue 325: When are Location's semantics trig… Willy Tarreau
- Re: issue 325: When are Location's semantics trig… Cameron Heavon-Jones
- Re: issue 325: When are Location's semantics trig… Julian Reschke
- Re: issue 325: When are Location's semantics trig… Cameron Heavon-Jones
- Re: issue 325: When are Location's semantics trig… Cameron Heavon-Jones
- Re: issue 325: When are Location's semantics trig… Julian Reschke
- Re: issue 325: When are Location's semantics trig… Cameron Heavon-Jones
- Re: issue 325: When are Location's semantics trig… Julian Reschke
- Re: issue 325: When are Location's semantics trig… Cameron Heavon-Jones
- Re: issue 325: When are Location's semantics trig… Daniel Stenberg
- Re: issue 325: When are Location's semantics trig… Willy Tarreau
- Re: issue 325: When are Location's semantics trig… Cameron Heavon-Jones
- Re: issue 325: When are Location's semantics trig… Daniel Stenberg
- Re: issue 325: When are Location's semantics trig… Cameron Heavon-Jones
- Re: issue 325: When are Location's semantics trig… Mark Nottingham
- Re: issue 325: When are Location's semantics trig… Willy Tarreau
- Re: issue 325: When are Location's semantics trig… Julian Reschke
- Re: issue 325: When are Location's semantics trig… Mark Nottingham
- Re: issue 325: When are Location's semantics trig… Julian Reschke
- Re: issue 325: When are Location's semantics trig… Mark Nottingham
- Re: issue 325: When are Location's semantics trig… Julian Reschke