Re: Fwd: I-D Action: draft-murchison-webdav-prefer-05.txt

Ken Murchison <murch@andrew.cmu.edu> Thu, 19 September 2013 15:33 UTC

Return-Path: <w3c-dist-auth-request@listhub.w3.org>
X-Original-To: ietfarch-webdav-archive@ietfa.amsl.com
Delivered-To: ietfarch-webdav-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 722AA21F997B for <ietfarch-webdav-archive@ietfa.amsl.com>; Thu, 19 Sep 2013 08:33:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.056
X-Spam-Level:
X-Spam-Status: No, score=-10.056 tagged_above=-999 required=5 tests=[AWL=0.543, 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 RkvDOJbQ4zfk for <ietfarch-webdav-archive@ietfa.amsl.com>; Thu, 19 Sep 2013 08:33:12 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id CE29921F96E4 for <webdav-archive@lists.ietf.org>; Thu, 19 Sep 2013 08:33:11 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <w3c-dist-auth-request@listhub.w3.org>) id 1VMgDb-0000wB-N0 for w3c-dist-auth-dist@listhub.w3.org; Thu, 19 Sep 2013 15:32:35 +0000
Resent-Date: Thu, 19 Sep 2013 15:32:35 +0000
Resent-Message-Id: <E1VMgDb-0000wB-N0@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <murch@andrew.cmu.edu>) id 1VMgDb-0000v6-6g for w3c-dist-auth@listhub.w3.org; Thu, 19 Sep 2013 15:32:35 +0000
Received: from smtp.andrew.cmu.edu ([128.2.11.96]) by lisa.w3.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from <murch@andrew.cmu.edu>) id 1VMgDZ-000421-VF for w3c-dist-auth@w3.org; Thu, 19 Sep 2013 15:32:35 +0000
Received: from [192.168.137.22] (cpe-76-180-197-142.buffalo.res.rr.com [76.180.197.142]) (user=murch mech=PLAIN (0 bits)) by smtp.andrew.cmu.edu (8.14.4/8.14.4) with ESMTP id r8JFW4Lx007366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 19 Sep 2013 11:32:05 -0400
Message-ID: <523B18F4.5060801@andrew.cmu.edu>
Date: Thu, 19 Sep 2013 11:32:04 -0400
From: Ken Murchison <murch@andrew.cmu.edu>
Organization: Carnegie Mellon University
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130514 Thunderbird/17.0.6
MIME-Version: 1.0
To: Julian Reschke <julian.reschke@gmx.de>
CC: WebDAV <w3c-dist-auth@w3.org>
References: <20130912172727.30588.2637.idtracker@ietfa.amsl.com> <52384537.1050901@gmx.de> <523AEB0A.7000504@gmx.de> <523AFB3A.2080709@andrew.cmu.edu> <523AFE31.5070600@gmx.de> <523B0490.9040203@andrew.cmu.edu> <523B0DDC.9010002@gmx.de>
In-Reply-To: <523B0DDC.9010002@gmx.de>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-PMX-Version: 5.5.9.388399, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.4.9.4220
X-SMTP-Spam-Clean: 8% ( BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, RDNS_GENERIC_POOLED 0, RDNS_POOLED 0, RDNS_RESIDENTIAL 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, RDNS_SUSP_SPECIFIC 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __RDNS_POOLED_2 0, __SANE_MSGID 0, __TO_MALFORMED_2 0, __USER_AGENT 0)
X-SMTP-Spam-Score: 8%
X-Scanned-By: MIMEDefang 2.60 on 128.2.11.96
Received-SPF: none client-ip=128.2.11.96; envelope-from=murch@andrew.cmu.edu; helo=smtp.andrew.cmu.edu
X-W3C-Hub-Spam-Status: No, score=-4.9
X-W3C-Hub-Spam-Report: AWL=-1.976, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.649
X-W3C-Scan-Sig: lisa.w3.org 1VMgDZ-000421-VF 3189c3e81731eb26623b2343a3575ef1
X-Original-To: w3c-dist-auth@w3.org
Subject: Re: Fwd: I-D Action: draft-murchison-webdav-prefer-05.txt
Archived-At: <http://www.w3.org/mid/523B18F4.5060801@andrew.cmu.edu>
Resent-From: w3c-dist-auth@w3.org
X-Mailing-List: <w3c-dist-auth@w3.org> archive/latest/13402
X-Loop: w3c-dist-auth@w3.org
Resent-Sender: w3c-dist-auth-request@w3.org
Precedence: list
List-Id: <w3c-dist-auth.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:w3c-dist-auth@w3.org>
List-Unsubscribe: <mailto:w3c-dist-auth-request@w3.org?subject=unsubscribe>

On 09/19/2013 10:44 AM, Julian Reschke wrote:
> On 2013-09-19 16:05, Ken Murchison wrote:
>> ...
>>>> The argument here is that we don't want the client to have to parse a
>>>> body if the request is successful.  Do you recommend that we 
>>>> specify 204
>>>> instead?
>>>
>>> The client doesn't need to parse the body, even if it's non empty.
>>
>> This is true, but including anything in the body defeats the purpose of
>> return=minimal.  The 2xx response code tells the client that all
>> instructions were performed successfully so there is no need for any
>> other verbiage.
>> ...
>
> I agree there's no need. I just wonder how strong the requirement no 
> to return anything is. I want to avoid a situation where clients blow 
> up just because they get a tiny status message.

Playing devil's advocate here: If a client sends return=minimal with a 
PROPATCH or MKCOL/MKCALENDAR and can't handle the minimal response, then 
its a bad client.  If it can't handle a minimal success response is MUST 
NOT send return=minimal.  Likewise, if a server can't properly send a 
minimal response, then it MUST NOT return Preference-Applied.

The more I think about this, I'm wondering why we can't specify that 
return=minimal requires an empty body upon success, or just specify that 
the server return 204.  If either a client or server can't implement it 
this way, then it is free to not use or ignore the preference.



>>> We can allow 204 as well; but we should stick with standard HTTP; and
>>> over there it's not uncommon that servers send a short text/plain or
>>> text/html result, even if it's not needed.
>>
>> OK.  How would you specify  the use of return=minimal with PROPPATCH and
>> MKCOL/MKCALENDAR, or do you think that it can't be applied to these
>> methods in the real world?
>
> Just state that the response can be any suitable success message (200, 
> 201, 204), and - for 200/201 - a response payload (a) is not needed 
> and (b) does not need to be processed.

I'd really like to nail this down, so there isn't a any variance in 
responses.  If we can't specify empty body, can we just go with 204?

-- 
Kenneth Murchison
Principal Systems Software Engineer
Carnegie Mellon University