IETF Logo Mail Archive

Re: Question regarding RFC 7230

James M Snell <jasnell@gmail.com> Mon, 09 January 2017 16:02 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 8CB0F129683 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 9 Jan 2017 08:02:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.72
X-Spam-Level:
X-Spam-Status: No, score=-9.72 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.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-3.199, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5nHTYJkLihdp for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Mon, 9 Jan 2017 08:02:47 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E035129681 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Mon, 9 Jan 2017 08:02:46 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1cQcM2-0002Uk-AZ for ietf-http-wg-dist@listhub.w3.org; Mon, 09 Jan 2017 15:59:26 +0000
Resent-Date: Mon, 09 Jan 2017 15:59:26 +0000
Resent-Message-Id: <E1cQcM2-0002Uk-AZ@frink.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by frink.w3.org with esmtps (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <jasnell@gmail.com>) id 1cQcLq-0002Tr-HC for ietf-http-wg@listhub.w3.org; Mon, 09 Jan 2017 15:59:14 +0000
Received: from mail-yw0-f170.google.com ([209.85.161.170]) by mimas.w3.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from <jasnell@gmail.com>) id 1cQcLk-00046h-II for ietf-http-wg@w3.org; Mon, 09 Jan 2017 15:59:09 +0000
Received: by mail-yw0-f170.google.com with SMTP id l75so11164921ywb.0 for <ietf-http-wg@w3.org>; Mon, 09 Jan 2017 07:58:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SrPyglS2vHvTQVXGbUBBrVu+vwl8s8D6OL+eJs1HHFA=; b=aE36IhesR5PN3WseYvRTaAt5E87g1/wJqPiAV70xEdcPcD4QxPVcECbXJ9uh5DwC2M vNMMx8nqKH4iiJFglQAEny0pMSLVxzwRtbI9CecgwsAR7TIPUKgjD7fJgxRqXuBONSSc K8wwzw2iGRKfrkWxv+ZkuDsGL5hGkRuRZX23z8Dz6az4wLbEfny4TnLXhPAjgQwHOd9R 4TtwtOTQFeSN0hbEzbV4u0p6VmwGbwC8iPD752aGPQBPlxq+XowVeOnDnMKqFLrkXo7f 8A5sTVecSlEzQw9MghFSvIvkpIMGQuOWIN3FuznqUEejXWW9YUsxn7h8uCSexHqQc/44 bqUg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SrPyglS2vHvTQVXGbUBBrVu+vwl8s8D6OL+eJs1HHFA=; b=CcwVJBR9FT3OyeXlub71Cy+By4EaZyP5qhljzAyfkH5nnOTKry/6/XKJIqaHENpZIm bP4YpntYabbimMf530fu3V0YBkjiEHF487VsMaJ0t+N5qusZZlHFJlXAV00O9eR9UBni 66nBwzOtrHZJfehnN9arpY7O96/Kb2JedwqNf2efXGyCo/Ic5u6t7BMwqEdHPRGyAb3/ /q8jcXsL/G0RO1okkwd+qbtDeqLNBIn0JHTIuK63T+1NMZfvv+FgjaT+sfUs+5hipXmU RmvSiDtPG/DlnERx8k+O3LALmgo9xwYHmsIEwh37X/XI0wP0UaggSr+7TGf9aof6ydDh vgxw==
X-Gm-Message-State: AIkVDXKIbPRUhZHjwHJoj9r68KvxgZ9CqHicNvxnaJEED/T6HZYFfp4SvTR2pgumijJj7sogV7q5SUxScHN7lQ==
X-Received: by 10.129.154.12 with SMTP id r12mr88670212ywg.53.1483977521643; Mon, 09 Jan 2017 07:58:41 -0800 (PST)
MIME-Version: 1.0
Received: by 10.37.106.139 with HTTP; Mon, 9 Jan 2017 07:58:21 -0800 (PST)
In-Reply-To: <a539966a-ddce-58f3-b9d3-3ac491dc342a@gmx.de>
References: <f19dd347-2334-4d0d-83bb-116b03ff3a14@email.android.com> <a539966a-ddce-58f3-b9d3-3ac491dc342a@gmx.de>
From: James M Snell <jasnell@gmail.com>
Date: Mon, 09 Jan 2017 07:58:21 -0800
Message-ID: <CABP7Rbffpzp+aCM=RTrOtDgZFDwcPh0Zj47O3DSFz-HzYOr=jQ@mail.gmail.com>
To: Julian Reschke <julian.reschke@gmx.de>
Cc: "Hartford, Eric" <hartbeat@amazon.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Received-SPF: pass client-ip=209.85.161.170; envelope-from=jasnell@gmail.com; helo=mail-yw0-f170.google.com
X-W3C-Hub-Spam-Status: No, score=-7.3
X-W3C-Hub-Spam-Report: AWL=1.187, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1cQcLk-00046h-II be8d7793fc0cdf6dad077d16974c7387
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Question regarding RFC 7230
Archived-At: <http://www.w3.org/mid/CABP7Rbffpzp+aCM=RTrOtDgZFDwcPh0Zj47O3DSFz-HzYOr=jQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/33268
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>

Yes, this has been on my todo list to complete for a while and I've
had several folks waiting and asking for it but I simply have not had
the time. If anyone would like to take the effort over to get it done
I'd be happy to hand it off.

On Sat, Jan 7, 2017 at 11:25 PM, Julian Reschke <julian.reschke@gmx.de> wrote:
> On 2017-01-08 03:51, Hartford, Eric wrote:
>>>
>>> It would be helpful if you explained what you're looking for. A safe
>>
>> method that allows a request body, so data doesn't need to be sent as
>> part of the URI?
>>
>> Yes, as in a RESTful API, GET method is used for the concept of entity
>> retrieval, and if the parameters of the retrieve query are complex
>> enough it is unwieldy to use the path or query parameters of the URI,
>> and it becomes more appropriate to use the content body of the request.
>>  (Think database queries.) Yes I "can" just use a POST but conceptually
>> my operation is a retrieval and I would like to be able to use a GET for
>> a retrieval operation.
>
>
> This comes up every few months. I personally agree that we should do
> something about it. Latest effort was
> <https://tools.ietf.org/html/draft-snell-search-method-00>.
>
> Best regards, Julian
>
>

v2.23.0 | Report a Bug | By Email