Permitted characters for http keys
Roberto Peon <grmocg@gmail.com> Tue, 19 February 2013 20:47 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 078D221F880F for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 19 Feb 2013 12:47:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.534
X-Spam-Level:
X-Spam-Status: No, score=-10.534 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
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 RlqHqx7bwNqa for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 19 Feb 2013 12:47:33 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 754A621F87E1 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 19 Feb 2013 12:47:33 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1U7u4d-0003cO-GR for ietf-http-wg-dist@listhub.w3.org; Tue, 19 Feb 2013 20:45:59 +0000
Resent-Date: Tue, 19 Feb 2013 20:45:59 +0000
Resent-Message-Id: <E1U7u4d-0003cO-GR@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <grmocg@gmail.com>) id 1U7u4V-0003be-L2 for ietf-http-wg@listhub.w3.org; Tue, 19 Feb 2013 20:45:51 +0000
Received: from mail-oa0-f50.google.com ([209.85.219.50]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <grmocg@gmail.com>) id 1U7u4T-0005Q0-A3 for ietf-http-wg@w3.org; Tue, 19 Feb 2013 20:45:51 +0000
Received: by mail-oa0-f50.google.com with SMTP id l20so7242669oag.23 for <ietf-http-wg@w3.org>; Tue, 19 Feb 2013 12:45:23 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=MfJ9M2ryrA6SmlV08eHIRUSvGpgXMSsbBY5QcM+unUs=; b=Cr2HrieIG8TtazNB73IAfcfLPQIzTX898sCdUfsa+x/LORooErkjbeo7SyuQBWIVAk 6z1Vkpk9EeB6QQzIndUJNtFSTmnR1nkBDZc+WH9cUHoAJrjB7LLs5t/unjy/x8QYWSuK Jfa8J4MigdoSQp9XCBj/FSokr6+ZxPAUVDKWlVHvpP4ZMRp07jg+Xg0WkSMXItONZjmZ m5lNXFKJ1ae74Eu0FqWS8eJp97luizdKNxSFM0njXRm1X1vtWA19nVeZhcFt8I2+qUAc dJRb69huuZXdrxo3aGrG0TpVLakITw286DZ2Nn+IVQCxwRLo546/GR4bHH0ZHBoPOCWa kbkQ==
MIME-Version: 1.0
X-Received: by 10.182.183.2 with SMTP id ei2mr8033355obc.84.1361306722990; Tue, 19 Feb 2013 12:45:22 -0800 (PST)
Received: by 10.76.167.193 with HTTP; Tue, 19 Feb 2013 12:45:22 -0800 (PST)
Date: Tue, 19 Feb 2013 12:45:22 -0800
Message-ID: <CAP+FsNeBoV-V190kVAOHDQqy5yuXB2dVyBxs4svtZM-_+KjNcA@mail.gmail.com>
From: Roberto Peon <grmocg@gmail.com>
To: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="f46d04479f29a7798004d619eb60"
Received-SPF: pass client-ip=209.85.219.50; envelope-from=grmocg@gmail.com; helo=mail-oa0-f50.google.com
X-W3C-Hub-Spam-Status: No, score=-4.4
X-W3C-Hub-Spam-Report: AWL=-1.732, BAYES_00=-1.9, 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: maggie.w3.org 1U7u4T-0005Q0-A3 cc9fdaffe6e47909a01a5bec1688a4d1
X-Original-To: ietf-http-wg@w3.org
Subject: Permitted characters for http keys
Archived-At: <http://www.w3.org/mid/CAP+FsNeBoV-V190kVAOHDQqy5yuXB2dVyBxs4svtZM-_+KjNcA@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16686
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>
Right now I believe we allow a wider encoding for HTTP keys than is necessary. Does anyone know of any non-crazy use for character values > 127 in the header keys (because I really can't think of any)? -=R
- Permitted characters for http keys Roberto Peon
- Re: Permitted characters for http keys Martin Thomson
- Re: Permitted characters for http keys Martin J. Dürst
- Re: Permitted characters for http keys Mark Nottingham
- Re: Permitted characters for http keys James M Snell
- Re: Permitted characters for http keys Mark Nottingham
- Re: Permitted characters for http keys James M Snell
- #41: Header Block field name length Mark Nottingham
- Re: #41: Header Block field name length Amos Jeffries
- RE: #41: Header Block field name length RUELLAN Herve
- Re: #41: Header Block field name length Roberto Peon