Re: [hybi] Additional HTTP headers on upgrade request?
Willy Tarreau <w@1wt.eu> Wed, 21 July 2010 05:19 UTC
Return-Path: <w@1wt.eu>
X-Original-To: hybi@core3.amsl.com
Delivered-To: hybi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4874F3A6B2E for <hybi@core3.amsl.com>; Tue, 20 Jul 2010 22:19:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.84
X-Spam-Level:
X-Spam-Status: No, score=-3.84 tagged_above=-999 required=5 tests=[AWL=-1.797, BAYES_00=-2.599, HELO_IS_SMALL6=0.556]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NaFFnFGtfQFQ for <hybi@core3.amsl.com>; Tue, 20 Jul 2010 22:19:03 -0700 (PDT)
Received: from 1wt.eu (1wt.eu [62.212.114.60]) by core3.amsl.com (Postfix) with ESMTP id 662313A6A86 for <hybi@ietf.org>; Tue, 20 Jul 2010 22:19:03 -0700 (PDT)
Received: (from willy@localhost) by mail.home.local (8.14.4/8.14.4/Submit) id o6L5JAsm030194; Wed, 21 Jul 2010 07:19:10 +0200
Date: Wed, 21 Jul 2010 07:19:10 +0200
From: Willy Tarreau <w@1wt.eu>
To: Jamie Lokier <jamie@shareable.org>
Message-ID: <20100721051910.GH26999@1wt.eu>
References: <n2s188fcbce1005071111kd19e6f41m861eaeb593d88475@mail.gmail.com> <4BE5994E.4010701@webtide.com> <u2n188fcbce1005092125veaf94306u249a225bdd3925ca@mail.gmail.com> <B8058102-9589-4663-976D-217B939667DD@apple.com> <Pine.LNX.4.64.1007210038520.7242@ps20323.dreamhostps.com> <20100721011221.GC27243@shareable.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20100721011221.GC27243@shareable.org>
User-Agent: Mutt/1.4.2.3i
Cc: hybi@ietf.org
Subject: Re: [hybi] Additional HTTP headers on upgrade request?
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Jul 2010 05:19:05 -0000
On Wed, Jul 21, 2010 at 02:12:21AM +0100, Jamie Lokier wrote: > Ian Hickson wrote: > > On Fri, 7 May 2010, Doug Simpkinson wrote: > > > > > > In draft 76, the upgrade request is said to include cookies that may be > > > relevant, but no mention of other HTTP headers is made. > > > > > > What about other relevant HTTP headers such as User-Agent and > > > Accept-Language? Shouldn't these also be sent? > > > > What's the use case? > > > > If there are clear and important use cases that are best handled by adding > > new fields to the handshake, then we should add them. > > The use case for User-Agent, normally determined by the client > implementation (not the application running on top of the WebSocket > API), is to provide servers with unreliable but pragmatically useful > information about what client implementations are using the server. > > It is used for profiling, for general interest, for tracking what > clients may need to be supported if there are particular issues to be > avoided with some clients (such as a particular message that breaks > one of them), for tracking when clients with particular workarounds on > the server have fallen into sufficient misuse that the workarounds can > be removed, and for implementing specific workarounds for particular > recognised clients. And it's used a lot to act differently with smartphones. Maybe that could be used on the server side to try to group outgoing data into fewer packets in order to improve user experience or reduce communication costs. Willy
- [hybi] Additional HTTP headers on upgrade request? Doug Simpkinson
- Re: [hybi] Additional HTTP headers on upgrade req… Greg Wilkins
- Re: [hybi] Additional HTTP headers on upgrade req… Doug Simpkinson
- Re: [hybi] Additional HTTP headers on upgrade req… Greg Wilkins
- Re: [hybi] Additional HTTP headers on upgrade req… Maciej Stachowiak
- Re: [hybi] Additional HTTP headers on upgrade req… Ian Hickson
- Re: [hybi] Additional HTTP headers on upgrade req… Jamie Lokier
- Re: [hybi] Additional HTTP headers on upgrade req… Greg Wilkins
- Re: [hybi] Additional HTTP headers on upgrade req… Greg Wilkins
- Re: [hybi] Additional HTTP headers on upgrade req… Willy Tarreau
- Re: [hybi] Additional HTTP headers on upgrade req… Willy Tarreau
- Re: [hybi] Additional HTTP headers on upgrade req… Ian Hickson
- Re: [hybi] Additional HTTP headers on upgrade req… Jamie Lokier
- Re: [hybi] Additional HTTP headers on upgrade req… Jamie Lokier
- Re: [hybi] Additional HTTP headers on upgrade req… Ian Hickson
- Re: [hybi] Additional HTTP headers on upgrade req… Willy Tarreau
- Re: [hybi] Additional HTTP headers on upgrade req… John Tamplin
- Re: [hybi] Additional HTTP headers on upgrade req… Simone Bordet
- Re: [hybi] Additional HTTP headers on upgrade req… Greg Wilkins