IETF Logo Mail Archive

Re: Byte range PATCH

Eric J Bowman <mellowmutt@zoho.com> Tue, 09 August 2022 06:04 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@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 B1E98C14F73B for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 8 Aug 2022 23:04:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.759
X-Spam-Level:
X-Spam-Status: No, score=-7.759 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=pass (768-bit key) header.from=mellowmutt@zoho.com header.d=zoho.com; dkim=pass (1024-bit key) header.d=zoho.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WE2JwnDGi_J4 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 8 Aug 2022 23:04:30 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F3DDDC14F73A for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 8 Aug 2022 23:04:29 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1oLILh-00FfAA-Tp for ietf-http-wg-dist@listhub.w3.org; Tue, 09 Aug 2022 06:04:17 +0000
Resent-Date: Tue, 09 Aug 2022 06:04:17 +0000
Resent-Message-Id: <E1oLILh-00FfAA-Tp@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mellowmutt@zoho.com>) id 1oLILe-00Ff9C-Po for ietf-http-wg@listhub.w3.org; Tue, 09 Aug 2022 06:04:14 +0000
Received: from sender4-pp-o91.zoho.com ([136.143.188.91]) by mimas.w3.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <mellowmutt@zoho.com>) id 1oLILd-00AfvG-8G for ietf-http-wg@w3.org; Tue, 09 Aug 2022 06:04:14 +0000
ARC-Seal: i=1; a=rsa-sha256; t=1660025036; cv=none; d=zohomail.com; s=zohoarc; b=kA3gnAEV332H13/Nwh1FHGzFnICOP8bzvYpeI2KPUd95BRwHunLw2+TInihv79cVZn8+RfRT5MEvBNsQ1tsXGDllgoiO5aUe5Lv1aDsPBjMZOOdRH9zKUb+b92yihvwd6dG34Igf+81+aLk2Et5qi6NOUW/II5MF8KybwKkDVNo=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1660025036; h=Content-Type:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=dsq4pzcfweUiJ57laAYLY3fyJOSr91A6XtIHlQHx7ew=; b=V4U17suehFyA7yI8IDpo8V9XU3EjeHv6JlYBeR/4EUZN53rX0U5SjDoyeR9wm4aCfwGj3XisZbOz8x+H+xUUszVdBVZAIavIXJWK3AN1XSLbgIml+2Gl2GHmR08qLCdXzI3zKRiPs5SCPkz+h1QDeIsOuofLvoJo9QoT8mDCu1Q=
ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=zoho.com; spf=pass smtp.mailfrom=mellowmutt@zoho.com; dmarc=pass header.from=<mellowmutt@zoho.com>
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=zapps768; d=zoho.com; h=date:from:to:cc:message-id:in-reply-to:references:subject:mime-version:content-type:user-agent; b=qggY880vhtXySNTzIH6fMoF2odf6raqA6C07jXdadzFH4uwPjBz7gbAozz/L4mZN/tuvF9Hcv8jk LsHGi5zbcuznpAxwlJEu4M4AoiIi83nkyurpCxhWRrq0Kz7VBK+p
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1660025036; s=zm2022; d=zoho.com; i=mellowmutt@zoho.com; h=Date:Date:From:From:To:To:Cc:Cc:Message-Id:Message-Id:In-Reply-To:References:Subject:Subject:MIME-Version:Content-Type:Feedback-ID:Reply-To; bh=dsq4pzcfweUiJ57laAYLY3fyJOSr91A6XtIHlQHx7ew=; b=CuETvic+LZUcW8zmTBUQfk1WORnca54z4k8QlsIajghl5lS3buxbzHaloj9tl9jM xmNdY1fSsxNw5TVcOKEQJWcHQfREzpkwrA8XOS5bCe1OlztVGvNouIyuED37DTTbCl2 8Kv6mnsU0vLAaP2MhtSok+iLU00JMo/1vI7MmhNA=
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1660025034650135.94944776900422; Mon, 8 Aug 2022 23:03:54 -0700 (PDT)
Received: from [65.117.211.248] by mail.zoho.com with HTTP;Mon, 8 Aug 2022 23:03:54 -0700 (PDT)
Date: Mon, 08 Aug 2022 23:03:54 -0700
From: Eric J Bowman <mellowmutt@zoho.com>
To: Austin William Wright <aaa@bzfx.net>
Cc: Roberto Polli <robipolli@gmail.com>, ietf-http-wg <ietf-http-wg@w3.org>
Message-Id: <1828133d77b.10112854770874.8646090352104563359@zoho.com>
In-Reply-To: <734BB380-2BA8-45C2-BECB-2C33129FB168@bzfx.net>
References: <E511F4BD-B422-46DA-8409-EBBD684098A6@bzfx.net> <CAP9qbHWtNL+U1XBHi5566S54wV2iazk2TnwZSKA5NtRVswkd=w@mail.gmail.com> <1828086138e.d0af5fbd69268.3210279692370972800@zoho.com> <734BB380-2BA8-45C2-BECB-2C33129FB168@bzfx.net>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_175643_455910641.1660025034619"
Importance: Medium
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
Feedback-ID: rr080112270ce8a3ae783c6d8bdcbc3f450000dcc362aabe116c08f8a525914339f0120a4dfce317fcc6b921:zu080112273e0e19bca97a7f329bbe73a0000025df245a297c5d4a940845e2d499093c6f46252b299fe82b2f:rf08011232137eef1aadd85c1b141f7d24000004142ff56a4d03c87f53218e43954f1bec34efff9f7564ea5c011ec6c56f3fa731bbcb5c:ZohoMail
Received-SPF: pass client-ip=136.143.188.91; envelope-from=mellowmutt@zoho.com; helo=sender4-pp-o91.zoho.com
X-W3C-Hub-DKIM-Status: validation passed: (address=mellowmutt@zoho.com domain=zoho.com), signature is good
X-W3C-Hub-DKIM-Status: validation passed: (address=mellowmutt@zoho.com domain=mellowmutt@zoho.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-4.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1oLILd-00AfvG-8G 422029f4c375adf14b1389f6af283701
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Byte range PATCH
Archived-At: <https://www.w3.org/mid/1828133d77b.10112854770874.8646090352104563359@zoho.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40319
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: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

>

> PATCH is not causing anyone any trouble.

>



Then why is it the redheaded stepchild of HTTP methods, defined by its own RFC as opposed to being part of the core protocol?



>

> This proposal does not "overload” anything. If anything, 

> I’m writing this to avoid overloading PUT or POST with 

> semantics that may be misunderstood by origin servers.

>



Did you mean to say intermediaries? No origin server I've ever coded has ever misunderstood anything about the application it's serving, let alone the intended semantics of a chosen method.



>

> The PATCH semantics, by contrast, are being used exactly 

> as intended and understood.

> 







Sort of. RFC 5789 included "resource creation" sure. But do you have any examples of PATCH being used that way in the wild? I can't help but wonder if there isn't a good reason it took 12 years for this issue to come up. Like maybe the RFC got it wrong? PATCH's "update" semantics are understood, and (perhaps widely) used as intended.



Creation, not so much! Never occurred to me that it would be controversial, to think that updating something pre-assumes its existence, and should report an error otherwise. Creation via PATCH falls under my definition of "silent error correction" which makes it a "bad thing" in the HTTP universe.



-Eric

v2.23.0 | Report a Bug | By Email