Re: Delta Compression and UTF-8 Header Values

Willy Tarreau <w@1wt.eu> Sun, 10 February 2013 11:08 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 5F67221F85B8 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 10 Feb 2013 03:08:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.332
X-Spam-Level:
X-Spam-Status: No, score=-10.332 tagged_above=-999 required=5 tests=[AWL=0.115, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_ENC_UTF8=0.152]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9aR+W+mUqPVz for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 10 Feb 2013 03:08:11 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 61AC621F85AC for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 10 Feb 2013 03:08:11 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1U4UjI-0005tp-00 for ietf-http-wg-dist@listhub.w3.org; Sun, 10 Feb 2013 11:05:52 +0000
Resent-Date: Sun, 10 Feb 2013 11:05:52 +0000
Resent-Message-Id: <E1U4UjI-0005tp-00@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <w@1wt.eu>) id 1U4UjB-0005t1-LB for ietf-http-wg@listhub.w3.org; Sun, 10 Feb 2013 11:05:45 +0000
Received: from 1wt.eu ([62.212.114.60]) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <w@1wt.eu>) id 1U4Uj7-0005w9-JZ for ietf-http-wg@w3.org; Sun, 10 Feb 2013 11:05:45 +0000
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id r1AB5EQN012187; Sun, 10 Feb 2013 12:05:14 +0100
Date: Sun, 10 Feb 2013 12:05:14 +0100
From: Willy Tarreau <w@1wt.eu>
To: Poul-Henning Kamp <phk@phk.freebsd.dk>
Cc: Frédéric Kayser <f.kayser@free.fr>, ietf-http-wg@w3.org
Message-ID: <20130210110514.GR8712@1wt.eu>
References: <CABP7RbfRLXPpL4=wip=FvqD3DM7BM8PXi7uRswHAusXUmPO_xw@mail.gmail.com> <CE65E38D-A482-4EA9-BAF4-F6498F643A78@mnot.net> <511642E9.9010607@it.aoyama.ac.jp> <20130209133341.GA8712@1wt.eu> <op.wr8se6rpiw9drz@uranium.westinmy-starwoodgp.com> <A4C04DB9-2524-49EC-8774-AF2EBF3EA350@free.fr> <79640.1360489083@critter.freebsd.dk> <20130210101248.GQ8712@1wt.eu> <79811.1360492152@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <79811.1360492152@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=-4.0
X-W3C-Hub-Spam-Report: AWL=-2.081, BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1U4Uj7-0005w9-JZ cc63ea46a16f198f0b52e5e6bc58a3a1
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Delta Compression and UTF-8 Header Values
Archived-At: <http://www.w3.org/mid/20130210110514.GR8712@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16518
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 Sun, Feb 10, 2013 at 10:29:12AM +0000, Poul-Henning Kamp wrote:
> Content-Type: text/plain; charset=ISO-8859-1
> --------
> In message <20130210101248.GQ8712@1wt.eu>, Willy Tarreau writes:
> >On Sun, Feb 10, 2013 at 09:38:03AM +0000, Poul-Henning Kamp wrote:
> >> The only two places which care about the character-set of the URL,
> >> is the ultimate client and the ultimate server, to everybody else,
> >> it is just a sequence of opaque bits, which they must treat as a
> >> indivisible unit.
> >
> >It's not that much opaque when your "HTTP router" has to be able to
> >match part of that URL to decide where to route the requests. 
> 
> First of all, the only non-semantic criteria you can route HTTP
> requests on are the Host: header.  (Which we just pass to DNS,
> so we don't care if it is UTF-8 or not).
> 
> As soon as you look at the URL, you dive into semantics, and you
> had better have an agreement with the content-provider about what
> those semantics (including char-set) and routing-criteria should be.

The content provider is the same as the one which sets the routing rules.
The 2 typical uses are :
  - send static objects to a dedicated farm
  - bypass caches for definitely non-cacheable objects

I would love to see only configurations where Host is the only
criterion but real world differs from the ideal one.

Willy