#443: whitespace in request-target

Mark Nottingham <mnot@mnot.net> Wed, 08 May 2013 01:13 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 9577211E80D7 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 7 May 2013 18:13:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.579
X-Spam-Level:
X-Spam-Status: No, score=-10.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, 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 hNUT0wNG6Pop for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 7 May 2013 18:12:54 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id DAE0C11E80D1 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 7 May 2013 18:12:50 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UZsuw-0005kq-O4 for ietf-http-wg-dist@listhub.w3.org; Wed, 08 May 2013 01:11:38 +0000
Resent-Date: Wed, 08 May 2013 01:11:38 +0000
Resent-Message-Id: <E1UZsuw-0005kq-O4@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1UZsuh-0005jL-I2 for ietf-http-wg@listhub.w3.org; Wed, 08 May 2013 01:11:23 +0000
Received: from mxout-07.mxes.net ([216.86.168.182]) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <mnot@mnot.net>) id 1UZsug-0000GJ-Ln for ietf-http-wg@w3.org; Wed, 08 May 2013 01:11:23 +0000
Received: from [192.168.1.80] (unknown [118.209.105.214]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 6FE6E22E253; Tue, 7 May 2013 21:10:59 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <20130430055251.GC21517@1wt.eu>
Date: Wed, 08 May 2013 11:10:56 +1000
Cc: Amos Jeffries <squid3@treenet.co.nz>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D9D88156-CB19-48ED-91FE-08DF56D2B6DD@mnot.net>
References: <2183465A-F833-4701-A55C-EC105A36329E@mnot.net> <516F6CF9.30709@treenet.co.nz> <84716645-4097-4014-BB4A-3A8C5BF5DD4E@mnot.net> <20130430055251.GC21517@1wt.eu>
To: Willy Tarreau <w@1wt.eu>
X-Mailer: Apple Mail (2.1503)
Received-SPF: pass client-ip=216.86.168.182; envelope-from=mnot@mnot.net; helo=mxout-07.mxes.net
X-W3C-Hub-Spam-Status: No, score=-3.4
X-W3C-Hub-Spam-Report: AWL=-3.386, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1UZsug-0000GJ-Ln 0131219f1a3689a9a4e10a3542f814e4
X-Original-To: ietf-http-wg@w3.org
Subject: #443: whitespace in request-target
Archived-At: <http://www.w3.org/mid/D9D88156-CB19-48ED-91FE-08DF56D2B6DD@mnot.net>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/17884
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>

I think that's going beyond the scope of this issue, which was really just about the strength of the requirement.

Since then, we've adjusted the semantics of SHOULD, and I think we can close this ticket as WONTFIX.

Cheers,


On 30/04/2013, at 3:52 PM, Willy Tarreau <w@1wt.eu> wrote:

>    Clients MUST NOT send user-typed delimiters and embedded whitespaces
>    as-is in URIs, and SHOULD either encode them, strip them. Alternatively
>    they MAY simply refuse to perform the request.
> 
>    Servers and intermediaries MUST NOT try to fix embedded spaces and
>    delimiters in URIs, as doing so could lead to interoperability issues
>    and make several components in the chain understand different things.
>    When a request does not parse exactly as defined in the ABNF, an error
>    400 (Bad Request) MUST be returned to the client.

--
Mark Nottingham   http://www.mnot.net/