Return-Path: 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 CE35721F84DF for ; Mon, 20 May 2013 11:54:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.598 X-Spam-Level: X-Spam-Status: No, score=-10.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, 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 a+lnFP+yYETH for ; Mon, 20 May 2013 11:54:23 -0700 (PDT) Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 7A52E21F9600 for ; Mon, 20 May 2013 11:54:23 -0700 (PDT) Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from ) id 1UeVCb-0004pS-TJ for ietf-http-wg-dist@listhub.w3.org; Mon, 20 May 2013 18:52:57 +0000 Resent-Date: Mon, 20 May 2013 18:52:57 +0000 Resent-Message-Id: Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from ) id 1UeVCQ-0004mj-Hn for ietf-http-wg@listhub.w3.org; Mon, 20 May 2013 18:52:46 +0000 Received: from mail-oa0-f49.google.com ([209.85.219.49]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from ) id 1UeVCP-0006IZ-TS for ietf-http-wg@w3.org; Mon, 20 May 2013 18:52:46 +0000 Received: by mail-oa0-f49.google.com with SMTP id k14so8217048oag.36 for ; Mon, 20 May 2013 11:52:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Jue78px2Pqgl+Gz7JH+zxOugEUg/Sev5hXempDo93FE=; b=wIBhyQ1DBZnzIUSaLjpC4Y76HjZEJhoqD+Y2jn+IrYiS0q/9JCBqCC31Ry23gCF/ez UXLa+N2AYI7GQCrFPPmnx4Hw743JVvJQBOCK9s5j1FdHXEYljrUNoYZxXKdUjtyiRBun rdDw9LYJYeDMMFAPxMgMOnM3n6CfK7lo5V4DvJhghU3g5gV6eHKTF7mLjqG9xRVCR99o ASpXFGcBZDWxgFYS5wKHocUu3eys3cGQ6eh+GRsxI/DY4JP44s1F4A8/7iTQ3m5/Xry1 ObAHgrovy+yIHIo3ACE0VKUQzfFYqc4D5atRMb9c8D0tWRj2U6d0MEHqaAAnBswhkH9I MUgQ== MIME-Version: 1.0 X-Received: by 10.60.155.177 with SMTP id vx17mr30793722oeb.9.1369075938723; Mon, 20 May 2013 11:52:18 -0700 (PDT) Received: by 10.76.131.232 with HTTP; Mon, 20 May 2013 11:52:18 -0700 (PDT) In-Reply-To: References: <85664EE9-3872-4A43-B7BA-1925FEFF0E81@mnot.net> Date: Mon, 20 May 2013 11:52:18 -0700 Message-ID: From: Roberto Peon To: Martin Thomson Cc: Mark Nottingham , HTTP Working Group Content-Type: multipart/alternative; boundary=089e010d8124ff920704dd2ad457 Received-SPF: pass client-ip=209.85.219.49; envelope-from=grmocg@gmail.com; helo=mail-oa0-f49.google.com X-W3C-Hub-Spam-Status: No, score=-3.5 X-W3C-Hub-Spam-Report: AWL=-2.689, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001 X-W3C-Scan-Sig: lisa.w3.org 1UeVCP-0006IZ-TS c070e60e8b9eef0727110f68f29b24ce X-Original-To: ietf-http-wg@w3.org Subject: Re: "Magic" string Archived-At: Resent-From: ietf-http-wg@w3.org X-Mailing-List: archive/latest/18044 X-Loop: ietf-http-wg@w3.org Resent-Sender: ietf-http-wg-request@w3.org Precedence: list List-Id: List-Help: List-Post: List-Unsubscribe: --089e010d8124ff920704dd2ad457 Content-Type: text/plain; charset=ISO-8859-1 For this bike shed, the shorter while still being effective, the better. -=R On Mon, May 20, 2013 at 10:05 AM, Martin Thomson wrote: > On 19 May 2013 20:22, Mark Nottingham wrote: > > We've currently incorporated the magic as: > > > >> The client connection header is a sequence of 25 octets (in hex > notation) > >> > >> 464f4f202a20485454502f322e300d0a0d0a4241520d0a0d0a > >> (the string FOO * HTTP/2.0\r\n\r\nBAR\r\n\r\n) followed by a SETTINGS > frame (Section 3.8.4). > > > > That string was based upon the quick testing I did a while back. > > > > I'm curious to know how people feel about this; while it's cosmetic, do > we want to do something a little more... expected, like: > > > > START * HTTP/2.0\r\n\r\nGO\r\n\r\n > > I don't care. Existence > colour for this particular bike shed. > > But I do know that 5 characters isn't going to fly. I know at least > one (major) implementation that only expects 3 or 4 characters before > the space. > > --089e010d8124ff920704dd2ad457 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
For this bike shed, the shorter while still being effectiv= e, the better.

-=3DR


On Mon, May 20, 2013 at 10:05 A= M, Martin Thomson <martin.thomson@gmail.com> wrote:
On 19 May 2013 20:22, Mark= Nottingham <mnot@mnot.net> wrot= e:
> We've currently incorporated the magic as:
>
>> The client connection header is a sequence of 25 octets (in hex no= tation)
>>
>> 464f4f202a20485454502f322e300d0a0d0a4241520d0a0d0a
>> (the string FOO * HTTP/2.0\r\n\r\nBAR\r\n\r\n) followed by a SETTI= NGS frame (Section 3.8.4).
>
> That string was based upon the quick testing I did a while back.
>
> I'm curious to know how people feel about this; while it's cos= metic, do we want to do something a little more... expected, like:
>
> START * HTTP/2.0\r\n\r\nGO\r\n\r\n

I don't care. =A0Existence > colour for this particular bike s= hed.

But I do know that 5 characters isn't going to fly. =A0I know at least<= br> one (major) implementation that only expects 3 or 4 characters before
the space.


--089e010d8124ff920704dd2ad457--