Re: GET / DELETE request bodies

Cory Benfield <cory@lukasa.co.uk> Mon, 17 February 2020 09:57 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 E58EE120808 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 17 Feb 2020 01:57:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.651
X-Spam-Level:
X-Spam-Status: No, score=-2.651 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lukasa-co-uk.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fShEAH2viqNK for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 17 Feb 2020 01:57:45 -0800 (PST)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 167C91207FF for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 17 Feb 2020 01:57:42 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1j3d6l-0002rI-5q for ietf-http-wg-dist@listhub.w3.org; Mon, 17 Feb 2020 09:54:31 +0000
Resent-Date: Mon, 17 Feb 2020 09:54:31 +0000
Resent-Message-Id: <E1j3d6l-0002rI-5q@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <cory@lukasa.co.uk>) id 1j3d6e-0002qX-Qa for ietf-http-wg@listhub.w3.org; Mon, 17 Feb 2020 09:54:24 +0000
Received: from mail-lj1-x235.google.com ([2a00:1450:4864:20::235]) by mimas.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from <cory@lukasa.co.uk>) id 1j3d6a-0008HY-ID for ietf-http-wg@w3.org; Mon, 17 Feb 2020 09:54:24 +0000
Received: by mail-lj1-x235.google.com with SMTP id x7so18101876ljc.1 for <ietf-http-wg@w3.org>; Mon, 17 Feb 2020 01:54:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lukasa-co-uk.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=MaOgyp1TrrqWrTXKbRRFwehl9tScIWqet5LAOlKAfhc=; b=X6st05EEDoDNkv7K9p+1Ndirs0nxR4us6BoulyPyD4LqTpWZmu8juApoC0fZ1nLDi0 42dWdF+jJv6fbzz33Vvra7eM9vneDMcfoohCjsW2RzfhdHahD6TS+uiYkA1ewA30govr gtf3ba6Zi2+TYQbbZjHC8duD0ZPnAUgdiAnlL/f8Fh3RnGDRPpSTNdEm2S06QDqNDPAB h61qLqfdNKorTkTfFHARzSA0FVy1zYSbpo6rWp/f2bAMBLC7jX4LlMspKSyptArYSjTu neH2Kw9JDe0NFklSWjivlRzQXzbFe1I5byGHeyXiRIsu9EIfdsKzmoCTl2U4mtjBT3pr M+OA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=MaOgyp1TrrqWrTXKbRRFwehl9tScIWqet5LAOlKAfhc=; b=S3X78f/cjN3WHhT+JHK7SbwWMPN8P9rpqqV4Jbm+EgFTqtQeH5mCAa/YQhTXr74uNJ vkv7pkXAQrBVLlEK3YF2bziRPtcMmgPMbVgIft/8xzY4/B/SqQ+aTd+te0CjSCAOpPeJ cFxTYFXJ/qkkUyWwZLoLGBk0JrNKfGOBHV7O7l/3144ubVAVKI5tOe/64bpoxfPfd+Ke 4Jlb+Qe8DVBICM742aFm733clVDgngDCpQ3QAlW76tI5vXoaBS1SQSBbv8in1dvbBfVx fBAUxJ4iBF6QFpUkgJ5VhGKHMA/XffwZY8seBfNjXn5hFJ6Vpz8BZysgy5BnZ64LUiGy KBsA==
X-Gm-Message-State: APjAAAU6gS+kOKYxHcxFTH/9yvPMuXO/k0XoFI4GctB4WUxpB5BSh4jZ iVO2xx/yG51VxNZcngwyd9GCRkLvKRj7l/Ej6dwY/g==
X-Google-Smtp-Source: APXvYqzRC3Ejdtfv7TP0Ju8Cxx6zkXat9DgJNqA7eVlaNILTTtSqd2gN92HzDuVuzyvKatNf/USg3eSpe4LSwTuuNK4=
X-Received: by 2002:a2e:b0c9:: with SMTP id g9mr9657574ljl.134.1581933248267; Mon, 17 Feb 2020 01:54:08 -0800 (PST)
MIME-Version: 1.0
References: <CAChr6SyZN4ceSeHkfQVnKRX7=RPnKjX_vAsL1mTHs18-MKRphQ@mail.gmail.com>
In-Reply-To: <CAChr6SyZN4ceSeHkfQVnKRX7=RPnKjX_vAsL1mTHs18-MKRphQ@mail.gmail.com>
From: Cory Benfield <cory@lukasa.co.uk>
Date: Mon, 17 Feb 2020 09:53:57 +0000
Message-ID: <CAH_hAJEdM+NeVKAwEC+8uQf_0Dv-ArEtetuSoOW3wcV9WMeMZw@mail.gmail.com>
To: Rob Sayre <sayrer@gmail.com>
Cc: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Received-SPF: pass client-ip=2a00:1450:4864:20::235; envelope-from=cory@lukasa.co.uk; helo=mail-lj1-x235.google.com
X-W3C-Hub-Spam-Status: No, score=-3.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1j3d6a-0008HY-ID cb3761de952a43d6657a9c7797a4848e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: GET / DELETE request bodies
Archived-At: <https://www.w3.org/mid/CAH_hAJEdM+NeVKAwEC+8uQf_0Dv-ArEtetuSoOW3wcV9WMeMZw@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/37356
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>

The semantic requirement missing is that DELETE bodies have no
spec-defined semantics. This is not that they can't have semantics, or
that they shouldn't have spec-defined semantics, only that no
specification has ever said what a body in a DELETE request means.
They never have. The result of this is that DELETES with bodies aren't
interoperable: while they may work with a specific service, that
service has defined a special-case for itself. Arbitrary
implementations are free to ignore DELETE requests with bodies, or
reject them, or do anything else they like with them.

The relevant section of the HTTP specification that discusses what it
means for a message body to have semantics is RFC 7231 ยง 3.3 (Payload
Semantics) (https://tools.ietf.org/html/rfc7231#section-3.3).

On Wed, 12 Feb 2020 at 08:30, Rob Sayre <sayrer@gmail.com> wrote:
>
> Hi,
>
> I saw
>
> https://github.com/httpwg/http-core/pull/300
>
> It's true that the semantics here aren't defined, but I've generally seen this stuff used when the request data won't fit in the request line.
>
> What semantic requirement is missing vs the request line? Some carriage returns?
>
> thanks,
> Rob