Re: Redirection to Other IP Addresses

Bin Ni <> Fri, 09 August 2019 00:03 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 2A6A112007A for <>; Thu, 8 Aug 2019 17:03:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, GB_VISITOURSITE=2, HEADER_FROM_DIFFERENT_DOMAINS=0.201, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id bDKWMNS9yayD for <>; Thu, 8 Aug 2019 17:03:55 -0700 (PDT)
Received: from ( [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 (Postfix) with ESMTPS id 1C4B7120025 for <>; Thu, 8 Aug 2019 17:03:55 -0700 (PDT)
Received: from lists by with local (Exim 4.89) (envelope-from <>) id 1hvsM6-00022g-R9 for; Fri, 09 Aug 2019 00:02:02 +0000
Resent-Date: Fri, 09 Aug 2019 00:02:02 +0000
Resent-Message-Id: <>
Received: from ([2603:400a:ffff:804:801e:34:0:4c]) by with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from <>) id 1hvsM4-00020Z-3A for; Fri, 09 Aug 2019 00:02:00 +0000
Received: from ([2607:f8b0:4864:20::e34]) by with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.89) (envelope-from <>) id 1hvsM2-0004Zt-CD for; Fri, 09 Aug 2019 00:01:59 +0000
Received: by with SMTP id m23so64312754vso.1 for <>; Thu, 08 Aug 2019 17:01:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=/VaHDS0cgfvHiNXiLHLFC7RR8aLleKSzN3aLUX0x8Cg=; b=GMeTdEXI1i9zEmrNaC0CYQEm57If636qtA2Rt1/3aV2kFzfvqfebA0fY/PcrmRylQL 0f3+uQxZc2lD7t/VuL2r8lJnPsneIjTgc4YNEjXn/vpwSsjKcoETc9JWALvZyqUp6ePD JBVwXJECXbaDq809xYV2McGLeDRjxD9XmAV9rZHSe+yP2n14oTrjGu2QOnYFLkuzXbSt +Xj5rkojWZwzA04RIkW7DRlSnWtAUKJqIAAXgbwNcIVVO+HvT1xZy6KzXG5TuZnTHdqR UA+CbVtCHXQXBQZyOunUDE1MmriwaAKnRmTDA8Nlo1vstAQEW80Np/7JfIu+th5JFZsw GN/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=/VaHDS0cgfvHiNXiLHLFC7RR8aLleKSzN3aLUX0x8Cg=; b=f8YItGjuktpamA1KoKBgK/DpAMbHg09BLANSnAwxsez7WTt8ZjMDbMYmDZFuujERVr BzgO6os7DA364KZv6Z0Oe7cL3Tpwtn7+jJYClZZ4hrhrZQO6/Gp24S+GlyjnT8tr9fuf +CsaUBXkaBprd6iDbi89HoD6QPd+dR4wVYef0FvKaAVO18nUT0bi3EzKmiRjGmrcmaCN YhHfMY38uOBE1JSHSKYdIbruuoruWEjXpatiHaubXLDVGm9Czuq8SR3J8nB4BmVeqy5+ S/M/QsBiSGNTK1zNhjbyUvw1WK4sHz5inPt/BFvL6ptp043ibSlDDaf+YsKwh5KZQ+x/ OO9g==
X-Gm-Message-State: APjAAAVyAj95VJz8XKtZGb1ktQgZIwmvmukfTU5/Vpp7bejcQUq7RKdq ZV8+XQzOeyyVzmepn/QJQD9rWkUbM4mU1yGizJ7nDOXqH90=
X-Google-Smtp-Source: APXvYqwUULPoxT+J8ngiw4H04JFd4B83uZRB/eKeGuxmGuR2Sc0Rr1HkxGil/qXa0nlfnG8aw/gepIznqFy34G6xSQg=
X-Received: by 2002:a67:e296:: with SMTP id g22mr11319503vsf.174.1565308896775; Thu, 08 Aug 2019 17:01:36 -0700 (PDT)
MIME-Version: 1.0
References: <>
In-Reply-To: <>
From: Bin Ni <>
Date: Thu, 8 Aug 2019 17:01:25 -0700
Message-ID: <>
To: "" <>
Content-Type: multipart/alternative; boundary="000000000000c1a276058fa3e00e"
Received-SPF: pass client-ip=2607:f8b0:4864:20::e34;;
X-W3C-Hub-Spam-Status: No, score=-3.2
X-W3C-Hub-Spam-Report: AWL=0.715, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: 1hvsM2-0004Zt-CD 225c56900c07913a5bca2d9aea1b677e
Subject: Re: Redirection to Other IP Addresses
Archived-At: <>
X-Mailing-List: <> archive/latest/36958
Precedence: list
List-Id: <>
List-Help: <>
List-Post: <>
List-Unsubscribe: <>

Hi All,

Thanks you all for the discussion in the past few weeks.
Hopefully I have addressed all the questions and concerns.
Now I wonder what is the procedure to make it a formal RFC?
Can someone point me a direction?


On Tue, Jul 23, 2019 at 4:32 PM Bin Ni <> wrote:

> Hi All,
> We trying to propose an addition to the HTTP protocol to support
> redirecting client to other IP addresses.
> The background is many website owners and CDN providers want the web or
> proxy servers to be able to participate in load balancing. For example,
> when the server is overloaded, redirect the request to some other servers;
> or based on the geo information of client IP address, send the client to a
> server that can provide better performance. Compare to the DNS-based load
> balancing, this method is more real time and more accurate. It can also
> take the URL, headers or other components in the HTTP request into
> consideration.
> What they can use today is the 30X redirection, which has at least the
> following limitations:
> 1. breaks the cookie, if you 30x redirect to another hostname or IP
> address.
> 2. breaks https if you redirect to another IP address.
> We need another way of telling the client/browser to only change the IP
> address but keep everything else the same.
> We put the proposal in a google doc at:
> You can post your questions and comment in the document or reply to this
> email.
> If this is not the correct way to submit a proposal, someone please point
> me to the right direction.
> Thanks!
> --
> Bin Ni


Bin Ni
VP of Engineering
[image: Quantil]

Connecting users with's that simple.

Office: +1-888-847-9851 <(888)%20847-9851>

[image: Tweeter] <>  [image: Google Plus]
<>  [image: Linked In]

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
or visit our website at <>