Re: HTTP router point-of-view concerns

Willy Tarreau <w@1wt.eu> Sat, 13 July 2013 19:34 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 E9EB421F9CD9 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 13 Jul 2013 12:34:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 QDqv47iV1E4x for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 13 Jul 2013 12:33:55 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id B106E21F8F09 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 13 Jul 2013 12:33:55 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Uy5Yq-00041c-HG for ietf-http-wg-dist@listhub.w3.org; Sat, 13 Jul 2013 19:32:52 +0000
Resent-Date: Sat, 13 Jul 2013 19:32:52 +0000
Resent-Message-Id: <E1Uy5Yq-00041c-HG@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <w@1wt.eu>) id 1Uy5Yi-00040C-Q6 for ietf-http-wg@listhub.w3.org; Sat, 13 Jul 2013 19:32:44 +0000
Received: from 1wt.eu ([62.212.114.60]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <w@1wt.eu>) id 1Uy5Yh-0002QE-W7 for ietf-http-wg@w3.org; Sat, 13 Jul 2013 19:32:44 +0000
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id r6DJUq0B002887; Sat, 13 Jul 2013 21:30:52 +0200
Date: Sat, 13 Jul 2013 21:30:52 +0200
From: Willy Tarreau <w@1wt.eu>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Sam Pullara <spullara@gmail.com>, Mark Nottingham <mnot@mnot.net>, James M Snell <jasnell@gmail.com>, Martin Thomson <martin.thomson@gmail.com>, Amos Jeffries <squid3@treenet.co.nz>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <20130713193052.GP32054@1wt.eu>
References: <092D65A8-8CB7-419D-B6A4-77CAE40A0026@gmail.com> <3835.1373612286@critter.freebsd.dk> <CD9E163F-1225-4DA8-9982-8BDBD16B1051@mnot.net> <1772.1373629495@critter.freebsd.dk> <20130712125628.GC28893@1wt.eu> <881777F8-86A7-4943-9BBD-8EB2DC306834@gmail.com> <20130713173222.GM32054@1wt.eu> <6782.1373741000@critter.freebsd.dk> <20130713191202.GN32054@1wt.eu> <6933.1373743292@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <6933.1373743292@critter.freebsd.dk>
User-Agent: Mutt/1.4.2.3i
Received-SPF: pass client-ip=62.212.114.60; envelope-from=w@1wt.eu; helo=1wt.eu
X-W3C-Hub-Spam-Status: No, score=-3.0
X-W3C-Hub-Spam-Report: AWL=-3.035, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01
X-W3C-Scan-Sig: lisa.w3.org 1Uy5Yh-0002QE-W7 eae6cc699ac792b684b6ad46aa2379e9
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTP router point-of-view concerns
Archived-At: <http://www.w3.org/mid/20130713193052.GP32054@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18752
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 Sat, Jul 13, 2013 at 07:21:32PM +0000, Poul-Henning Kamp wrote:
> In message <20130713191202.GN32054@1wt.eu>, Willy Tarreau writes:
> 
> >No problem but we really need the server side to be able to adjust
> >part of this field.
> 
> Could you oblige me with an example, since I seem unable to come
> up with one myself ?

Yes. Client picks a random session ID with the highest 16 bits = 0,
sends the request to the first server. The load balancer overthere
puts the DC ID and the local server ID in these bits and sends this
ID back to the client along with the response. When upon a subsequent
request the client is directed to a different DC, the information
about the location of the client's context is found and the context
can be retrieved.

Willy


> 
> -- 
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe    
> Never attribute to malice what can adequately be explained by incompetence.