can a conditional header field put conditions on resources other than the target resource?

Julian Reschke <julian.reschke@gmx.de> Fri, 25 January 2013 14:48 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 905A521F8468 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 25 Jan 2013 06:48:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.961
X-Spam-Level:
X-Spam-Status: No, score=-9.961 tagged_above=-999 required=5 tests=[AWL=0.638, BAYES_00=-2.599, 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 eqi-YRMYNyvQ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Fri, 25 Jan 2013 06:48:36 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id EEDAD21F844F for <httpbisa-archive-bis2Juki@lists.ietf.org>; Fri, 25 Jan 2013 06:48:35 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1TykYu-0003jO-G7 for ietf-http-wg-dist@listhub.w3.org; Fri, 25 Jan 2013 14:47:24 +0000
Resent-Date: Fri, 25 Jan 2013 14:47:24 +0000
Resent-Message-Id: <E1TykYu-0003jO-G7@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <julian.reschke@gmx.de>) id 1TykYn-0003if-IS for ietf-http-wg@listhub.w3.org; Fri, 25 Jan 2013 14:47:17 +0000
Received: from mout.gmx.net ([212.227.17.21]) by lisa.w3.org with esmtp (Exim 4.72) (envelope-from <julian.reschke@gmx.de>) id 1TykYi-0007rg-Ai for ietf-http-wg@w3.org; Fri, 25 Jan 2013 14:47:17 +0000
Received: from mailout-de.gmx.net ([10.1.76.34]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0Lvegk-1V5zMw0uwG-017RJc for <ietf-http-wg@w3.org>; Fri, 25 Jan 2013 15:46:46 +0100
Received: (qmail invoked by alias); 25 Jan 2013 14:46:45 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.102]) [217.91.35.233] by mail.gmx.net (mp034) with SMTP; 25 Jan 2013 15:46:45 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+RbX9weAyR8aMeyRZVCqkO6ux3c3PbVPeL/N0Cw1 +a0JK3UpmvxIvK
Message-ID: <51029ACD.60201@gmx.de>
Date: Fri, 25 Jan 2013 15:46:37 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130107 Thunderbird/17.0.2
MIME-Version: 1.0
To: "Roy T. Fielding" <fielding@gbiv.com>
CC: HTTP Working Group <ietf-http-wg@w3.org>
References: <51027F3E.6010904@gmx.de> <25AA4ADC-0DED-4F04-87D0-647A75CFC14A@gbiv.com>
In-Reply-To: <25AA4ADC-0DED-4F04-87D0-647A75CFC14A@gbiv.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Received-SPF: pass client-ip=212.227.17.21; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
X-W3C-Hub-Spam-Status: No, score=-3.3
X-W3C-Hub-Spam-Report: AWL=-3.300, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1TykYi-0007rg-Ai 52f3e0473422058c862cb157fddbd7e6
X-Original-To: ietf-http-wg@w3.org
Subject: can a conditional header field put conditions on resources other than the target resource?
Archived-At: <http://www.w3.org/mid/51029ACD.60201@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16219
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>

Looking at 
<http://svn.tools.ietf.org/svn/wg/httpbis/draft-ietf-httpbis/latest/p4-conditional.html#precedence>:

"... Other conditional request header fields, defined by extensions to 
HTTP, might place conditions on the state of the target resource in 
general, such as how the If header field in WebDAV has been defined to 
make a request conditional on the presence or absence of a lock [RFC4918]."

Actually, "If", as defined in RFC 2518 and 4918 can put conditions on 
resources other than the target resource, see the "Tagged-list" 
production in 
<http://greenbytes.de/tech/webdav/rfc4918.html#if.header.syntax>) -- 
should we rephrase P4 accordingly?

Best regards, Julian