Re: HTTP router point-of-view concerns

Willy Tarreau <w@1wt.eu> Sat, 13 July 2013 19:34 UTC

Resent-Date: Sat, 13 Jul 2013 19:32:52 +0000
Resent-Message-Id: <E1Uy5Yq-00041c-HG@frink.w3.org>
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
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
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

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.

HTTP router point-of-view concerns Christian Parpart
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Christian Parpart
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Michael Sweet
Re: HTTP router point-of-view concerns Martin Thomson
Re: HTTP router point-of-view concerns James M Snell
Re: HTTP router point-of-view concerns Sam Pullara
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Sam Pullara
Re: HTTP router point-of-view concerns Patrick McManus
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns James M Snell
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns James M Snell
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Sam Pullara
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Martin Thomson
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Mark Nottingham
Re: HTTP router point-of-view concerns Mike Belshe
Re: HTTP router point-of-view concerns Gábor Molnár
Re: HTTP router point-of-view concerns Gábor Molnár
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Michael Sweet
Re: HTTP router point-of-view concerns Christian Parpart
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Patrick McManus
Re: HTTP router point-of-view concerns Jeff Pinner
Re: HTTP router point-of-view concerns Martin Thomson
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Ludin, Stephen
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns James M Snell
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Amos Jeffries
Re: HTTP router point-of-view concerns Roberto Peon
Re: HTTP router point-of-view concerns Yoav Nir
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Sam Pullara
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Mark Delany
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Yoav Nir
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Yoav Nir
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Stephen Farrell
Re: HTTP router point-of-view concerns Willy Tarreau
Re: HTTP router point-of-view concerns Sam Pullara
Re: HTTP router point-of-view concerns Nicolas Mailhot
Re: HTTP router point-of-view concerns Nicolas Mailhot
Re: HTTP router point-of-view concerns Nicolas Mailhot
Re: HTTP router point-of-view concerns Martin Nilsson
Re: HTTP router point-of-view concerns Nico Williams
Re: HTTP router point-of-view concerns Nico Williams
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Nico Williams
Re: HTTP router point-of-view concerns Poul-Henning Kamp
Re: HTTP router point-of-view concerns Nico Williams