Re: HTTP router point-of-view concerns

Martin Thomson <martin.thomson@gmail.com> Fri, 12 July 2013 15:52 UTC

Resent-Date: Fri, 12 Jul 2013 15:51:54 +0000
Resent-Message-Id: <E1UxfdS-000737-Eo@frink.w3.org>
MIME-Version: 1.0
In-Reply-To: <CA+KJw_592N7xBVLceTXFQreP1-wUUHutmWii7LQ_mdkGR-7M_w@mail.gmail.com>
References: <CA+qvzFPUpcm6kUtJx+rTw8Dpp4Gtx4Bmr3XPDhjNsjchUfN9_w@mail.gmail.com> <51DE1E32.9010801@treenet.co.nz> <CAP+FsNdcYhA=V5Z+zbt70b5e7WmcmXgjG5M9L3vfXeXfTwmRnw@mail.gmail.com> <51DE327C.7010901@treenet.co.nz> <CABkgnnXeqD6wh0dcJ1Dz=4PLAJNkDeGcCuzMr9ATd_7xS7nbGQ@mail.gmail.com> <CABP7RbcUkLf3CTAB4jwicnsiKWLGVY6=hX0k=0256SR_gcVt9A@mail.gmail.com> <CAP+FsNcOZnLa9GCr6XcZNFdq-mSXG6Q-_1Lb5u=a2YyXNCsVfQ@mail.gmail.com> <51DFBDAB.9010505@treenet.co.nz> <CABaLYCs4KUXO2YwGyG07kbGJtrrfc7kVMJH3N_f=D-WQG86FcQ@mail.gmail.com> <CA+KJw_592N7xBVLceTXFQreP1-wUUHutmWii7LQ_mdkGR-7M_w@mail.gmail.com>
Date: Fri, 12 Jul 2013 08:51:19 -0700
Message-ID: <CABkgnnXOw-6vX_Ayy7cNDKi4GX3J4fREyUksCpLuS6XWvqTruw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Gábor Molnár <gabor.molnar@sch.bme.hu>
Cc: Mike Belshe <mike@belshe.com>, Amos Jeffries <squid3@treenet.co.nz>, httpbis mailing list <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=209.85.212.172; envelope-from=martin.thomson@gmail.com; helo=mail-wi0-f172.google.com
Subject: Re: HTTP router point-of-view concerns
Archived-At: <http://www.w3.org/mid/CABkgnnXOw-6vX_Ayy7cNDKi4GX3J4fREyUksCpLuS6XWvqTruw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

On 12 July 2013 02:46, Gábor Molnár <gabor.molnar@sch.bme.hu> wrote:
> The problem is that there's a DoS vector here. While sending the HEADERS
> frames on the upstream connection, there must not be anything else sent
> there. Now suppose a client is very slow, for example, it waits one second
> between sending the first and the second (last) HEADERS frame to the proxy.
> During this time (which can be arbitrary large), the proxy cannot send
> anything on its upstream connection (and it cannot create a new connection
> as it's forbidden in the current spec), so it's basically is blocked.

So don't do that then.

If you have to have two headers frames, then we simply don't create a
restriction like the current one whereby both have to appear in
immediate succession.

As has been suggested, if routing information is important, we can
conceive of ways to ensure that it appears first.  That doesn't
necessarily constrain the rest of the design.  And existing
constraints are a product of the existing design.  A changed design
necessarily creates new constraints.

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