- From: Bin Ni <nibin@quantil.com>
- Date: Tue, 23 Jul 2019 16:32:29 -0700
- To: "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
- Message-ID: <CAFifEMLOHp5=OqUXZbg_WKNQmNsTW3Bg5P4btJdX06CF=Wi2AA@mail.gmail.com>
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: https://docs.google.com/document/d/1gtF6Nq3iPe44515BfsU18dAxfCYOvQaekiezK8FEHu0/edit?usp=sharing 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 www.quantil.com
Received on Friday, 26 July 2019 08:49:21 UTC