IETF Logo Mail Archive

Re: Call for Adoption: SEARCH method

Philippe Mougin <pmougin@acm.org> Thu, 19 November 2020 06:47 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 26D983A101B for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 18 Nov 2020 22:47:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.649
X-Spam-Level:
X-Spam-Status: No, score=-2.649 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 NESTgtRDS7rw for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 18 Nov 2020 22:47:54 -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 D96853A101A for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 18 Nov 2020 22:47:54 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1kfdh4-0006RT-W7 for ietf-http-wg-dist@listhub.w3.org; Thu, 19 Nov 2020 06:45:23 +0000
Resent-Date: Thu, 19 Nov 2020 06:45:22 +0000
Resent-Message-Id: <E1kfdh4-0006RT-W7@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 <pmougin@acm.org>) id 1kfdh4-0006Qk-DV for ietf-http-wg@listhub.w3.org; Thu, 19 Nov 2020 06:45:22 +0000
Received: from smtp04.smtpout.orange.fr ([80.12.242.126] helo=smtp.smtpout.orange.fr) by mimas.w3.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.92) (envelope-from <pmougin@acm.org>) id 1kfdh2-0000Ev-DX for ietf-http-wg@w3.org; Thu, 19 Nov 2020 06:45:22 +0000
Received: from [192.168.1.13] ([86.252.35.207]) by mwinf5d60 with ME id u6l32300Y4U951A036l30c; Thu, 19 Nov 2020 07:45:05 +0100
X-ME-Helo: [192.168.1.13]
X-ME-Date: Thu, 19 Nov 2020 07:45:05 +0100
X-ME-IP: 86.252.35.207
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Philippe Mougin <pmougin@acm.org>
Mime-Version: 1.0 (1.0)
Date: Thu, 19 Nov 2020 07:45:05 +0100
Message-Id: <310FD09B-A408-4E9F-AC66-D83F9CA34B58@acm.org>
References: <CABP7RbeA8mj=sQhRFx6cUnnGES9=fogy=94nWwWkuQDj2NBNfA@mail.gmail.com>
Cc: Mark Nottingham <mnot@mnot.net>, Tommy Pauly <tpauly@apple.com>, HTTP Working Group <ietf-http-wg@w3.org>
In-Reply-To: <CABP7RbeA8mj=sQhRFx6cUnnGES9=fogy=94nWwWkuQDj2NBNfA@mail.gmail.com>
To: James M Snell <jasnell@gmail.com>
X-Mailer: iPhone Mail (17G80)
Received-SPF: softfail client-ip=80.12.242.126; envelope-from=pmougin@acm.org; helo=smtp.smtpout.orange.fr
X-W3C-Hub-Spam-Status: No, score=-4.2
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, W3C_AA=-1, W3C_DB=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1kfdh2-0000Ev-DX f9317f92a626ac2af540f54d505b48b9
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Call for Adoption: SEARCH method
Archived-At: <https://www.w3.org/mid/310FD09B-A408-4E9F-AC66-D83F9CA34B58@acm.org>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/38242
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>

> Le 19 nov. 2020 à 04:43, James M Snell <jasnell@gmail.com> a écrit
> 
> To be clear, this is not intended as a safe, idempotent equivalent to POST. It is intended specifically to cover search/query operations which are often ambiguously represented as GET or POST. I'm not quite sure what a safe idempotent equivalent to POST would even be, but this is not it. 

POST is often used to perform operations that are actually safe by nature, and it would be useful to have a method that could express that at the HTTP level. That's what I referred as a "safe/idempotent equivalent to POST". Essentially, such a method would subsume the SEARCH method described in the draft.

Best,
Philippe Mougin

v2.23.0 | Report a Bug | By Email