Re: Redirection to Other IP Addresses

"W. Felix Handte" <w@felixhandte.com> Thu, 01 August 2019 16:40 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 E18A21201B4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 1 Aug 2019 09:40:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level:
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_VISITOURSITE=2, HEADER_FROM_DIFFERENT_DOMAINS=0.201, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 MW21modKCpfD for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 1 Aug 2019 09:40:20 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [IPv6:2603:400a:ffff:804:801e:34:0:38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 064521200E0 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 1 Aug 2019 09:40:19 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.89) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1htE5B-0000W1-9D for ietf-http-wg-dist@listhub.w3.org; Thu, 01 Aug 2019 16:37:37 +0000
Resent-Date: Thu, 01 Aug 2019 16:37:37 +0000
Resent-Message-Id: <E1htE5B-0000W1-9D@frink.w3.org>
Received: from mimas.w3.org ([2603:400a:ffff:804:801e:34:0:4f]) by frink.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <w@felixhandte.com>) id 1htE57-0000VB-6N for ietf-http-wg@listhub.w3.org; Thu, 01 Aug 2019 16:37:33 +0000
Received: from felixhandte.com ([54.172.180.13] helo=mail.felixhandte.com) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <w@felixhandte.com>) id 1htE55-0007Tc-Lz for ietf-http-wg@w3.org; Thu, 01 Aug 2019 16:37:33 +0000
Received: from [172.30.220.221] (unknown [163.114.130.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.felixhandte.com (Postfix) with ESMTPSA id F01172CF4E; Thu, 1 Aug 2019 16:37:09 +0000 (UTC)
To: ietf-http-wg@w3.org, nibin@quantil.com
References: <CAFifEMLOHp5=OqUXZbg_WKNQmNsTW3Bg5P4btJdX06CF=Wi2AA@mail.gmail.com> <CAFifEMLnSB5SYb_q0toTE3Xy1i56=14ki=__91Phc76HHL+ZhQ@mail.gmail.com> <f05b5157-f068-1e03-8422-36d0425a32a5@treenet.co.nz> <CAFifEMLQXUSHKOjKN9JR87ht1UUvf-1AEWKNmuKeOqKyzjT28Q@mail.gmail.com> <CAJEGKNtWvXyrFLU0KW-rqN1qd-PLOqobjx1o6kRcH27_O9Ri7Q@mail.gmail.com> <CAFifEMKhjU=EmMj6yyVN5D1aSfCVi9HAWgE-Ebzu8NscKQpv_w@mail.gmail.com> <CAJEGKNvoKijzJsTOSE0w08wst=zxoTa95Jx8xVfRWmCWJTJ=4g@mail.gmail.com> <CAFifEMLrWwBoPDQZiHvp65zwS+0CEka1sSoLMYQo6ydYit3aNQ@mail.gmail.com> <CAAXAoJUdJP-WUa8sxt_3L+=09wQb_UUOGq0517ibzYrVoU8aOA@mail.gmail.com> <CAFifEMLvsHA9eOZS6MRNCvVa_c+jEOoPsmXbMrbC09aY=0-MZQ@mail.gmail.com> <CAAXAoJUvdPaFU-xjaVTC8J9=bLe6QfyEnsyHLM1EMUKN1HNtTg@mail.gmail.com> <alpine.DEB.2.20.1908010950240.24744@tvnag.unkk.fr> <CAFifEML6zwvKZJwO0P0L_bvOq8ow1U1j4UkfOTJf0CDRjL71ig@mail.gmail.com> <alpine.DEB.2.20.1908011055320.16907@tvnag.unkk.fr> <CAFifEMLECLpz=E1h7jBPY_5_KSzTRoV-ajc9aMLvEUB8RS68QQ@mail.gmail.com>
From: "W. Felix Handte" <w@felixhandte.com>
Message-ID: <0798f7aa-0fac-b7e0-a38d-2b0c781ae50d@felixhandte.com>
Date: Thu, 1 Aug 2019 12:37:09 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CAFifEMLECLpz=E1h7jBPY_5_KSzTRoV-ajc9aMLvEUB8RS68QQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Received-SPF: pass client-ip=54.172.180.13; envelope-from=w@felixhandte.com; helo=mail.felixhandte.com
X-W3C-Hub-Spam-Status: No, score=-3.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1htE55-0007Tc-Lz 2f129a2edf0991f10e81dda07054a118
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Redirection to Other IP Addresses
Archived-At: <https://www.w3.org/mid/0798f7aa-0fac-b7e0-a38d-2b0c781ae50d@felixhandte.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/36920
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: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Bin,

I've been following along on this discussion and it's still not clear to 
me why 30X doesn't solve this use case. Take for example a request and 
response as follows.

   GET /large_file HTTP/1.1
   Host: cdn.com

To which the server responds with

   HTTP/1.1 307
   Location: https://singapore.geo.cdn.com/large_file

Or even

   HTTP/1.1 307
   Location: https://123_45_67_89.ip.cdn.com/large_file

Maybe I'm missing something, but as I understand it, HTTPS and Cookies 
should work with the above (assuming you have wildcard certs for 
*.geo.cdn.com and/or *.ip.cdn.com, and have set your cookies with 
domain=.cdn.com). And it otherwise seems to accomplish exactly your intent.

Can you explain in a little more detail why you believe something along 
those lines wouldn't solve your need?

Thanks,
Felix

On 8/1/19 6:12 AM, Bin Ni wrote:
> Hi Daniel,
> 
> At high level, my proposal is in every other way the same as today's 30X 
> redirection.
> With this in mind, the answer to your questions are:
> 1. In general, the alternate IP should only be used once for the next 
> single request.
> But there is nothing to prevent the clients from remembering it, which 
> is OK.
> Just like there is nothing to prevent a client to disregard the DNS TTL.
> They do it with their own risk.
> 2. This proposal is to fix some limitations of the 30X with Location header.
> Not very helpful to make it work together with the Location header.
> 3. We are not requiring every server and every client to support this 
> proposal.
> For the ones who find it to be useful, the "extra burden" is a non-issue.
> 
> Thanks!
> 
> Bin
> 
> On Thu, Aug 1, 2019 at 2:18 AM Daniel Stenberg <daniel@haxx.se 
> <mailto:daniel@haxx.se>> wrote:
> 
>     On Thu, 1 Aug 2019, Bin Ni wrote:
> 
>      > 2. my proposed behavior:
>      > Client: Hi Server-1.1.1.1, can you send me the movie XXX?
>      > Server-1.1.1.1: Sorry, I can't give you the movie, you need to
>     ask server
>      > 2.2.2.2 for this movie.
>      > Client: Hi Server-2.2.2.2, can you send me the movie XXX?
>      > Server-2.2.2.2: Here is the movie.
>      > (It then took 0.5 hours to deliver the movie, because
>     server-2.2.2.2 is
>      > closer to the client, or less loaded)
> 
>     If we for a moment play with the idea that we'd do something like
>     this, then I
>     think it should be aligned with and work together with Alt-Svc in a
>     better way
>     than what is currently proposed...
> 
>     There's no max-age/TTL. For how long is the user-agent supposed to
>     consider
>     the alternative IP addresses as the only ones that the given origin
>     has?
>     Forever? Only for the next single connect (attempt)?
> 
>     Are the alternative IPs supposed to be used for the entire origin or
>     for that
>     specific URI only?
> 
>     A 3xx redirect without a Location: header? Wouldn't it make more
>     sense and
>     work more similar to existing 3xx redirects if it also sends a
>     Location:? Then
>     existing clients that don't understand 312 might have a higher
>     chance of at
>     least doing something sensible.
> 
>     If a client gets this response and starts downloading huge content
>     from the
>     new IP and the client then opens a second connection to the origin
>     in a second
>     tab. Which IPs is that supposed to use? The original ones or the
>     redirected
>     ones?
> 
>     Requring user-agent snooping for a server to figure out if the
>     feature works
>     or not is a totally broken idea and I think this detail needs to be
>     worked out
>     for this idea to be considered for real.
> 
>     My personal preference is probably to add some sort of "urgency"
>     thing to
>     alt-svc instead of this 312 plus several headers, so that a client
>     can be told
>     that it should switch sooner rather than later.
> 
>     -- 
> 
>        / daniel.haxx.se <http://daniel.haxx.se>
> 
> 
> 
> -- 
> 
> Bin Ni
> VP of Engineering
> 
> Quantil
> 
> Connecting users with content...it's that simple.
> 
> Office: +1-888-847-9851 <tel:(888)%20847-9851>
> 
> Tweeter <https://twitter.com/Team_Quantil> Google Plus 
> <https://plus.google.com/+Quantil_team/> Linked In 
> <https://www.linkedin.com/company/quantil>
> 
> The information contained in this email may be confidential and/or 
> legally privileged. It has been sent for the sole use of the intended 
> recipient(s). If the reader of this message is not an intended 
> recipient, you are hereby notified that any unauthorized review, use, 
> disclosure, dissemination, distribution, or copying of this 
> communication, or any of its contents, is strictly prohibited. If you 
> have received this communication in error, please reply to the sender 
> and destroy all copies of the message. To contact us directly, send to 
> QUANTIL, INC. at 1919 S Bascom Ave #600, Campbell, CA 95008 
> <https://maps.google.com/?q=1919+S+Bascom+Ave+%23600,+Campbell,+CA+95008&entry=gmail&source=g>;, 
> or visit our website at www.quantil.com. <https://www.quantil.com/>
>