Re: [Doh] POST and GET
Daniel Stenberg <daniel@haxx.se> Tue, 18 September 2018 06:18 UTC
Return-Path: <daniel@haxx.se>
X-Original-To: doh@ietfa.amsl.com
Delivered-To: doh@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C57C0130E16 for <doh@ietfa.amsl.com>; Mon, 17 Sep 2018 23:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 K4P57_elg-S5 for <doh@ietfa.amsl.com>; Mon, 17 Sep 2018 23:18:16 -0700 (PDT)
Received: from giant.haxx.se (www.haxx.se [IPv6:2a00:1a28:1200:9::2]) by ietfa.amsl.com (Postfix) with ESMTP id 8B33D130DED for <doh@ietf.org>; Mon, 17 Sep 2018 23:18:16 -0700 (PDT)
Received: from giant.haxx.se (mail [127.0.0.1]) by giant.haxx.se (8.15.2/8.15.2/Debian-4) with ESMTPS id w8I6IDQ0012355 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 18 Sep 2018 08:18:13 +0200
Received: from localhost (dast@localhost) by giant.haxx.se (8.15.2/8.15.2/Submit) with ESMTP id w8I6IB0E012342; Tue, 18 Sep 2018 08:18:11 +0200
X-Authentication-Warning: giant.haxx.se: dast owned process doing -bs
Date: Tue, 18 Sep 2018 08:18:11 +0200
From: Daniel Stenberg <daniel@haxx.se>
X-X-Sender: dast@giant.haxx.se
To: Sebastiaan Deckers <sebdeckers83@gmail.com>
cc: doh@ietf.org, Kenny Shen <kenny@machinesung.com>
In-Reply-To: <CADVGGb8+znpFStX4Qn3S4oCqOp1Np9uDPVXfS0V8nQecN3P+FA@mail.gmail.com>
Message-ID: <alpine.DEB.2.20.1809180813560.24774@tvnag.unkk.fr>
References: <CADVGGb8+znpFStX4Qn3S4oCqOp1Np9uDPVXfS0V8nQecN3P+FA@mail.gmail.com>
User-Agent: Alpine 2.20 (DEB 67 2015-01-07)
X-fromdanielhimself: yes
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/KK8vfebz9g8H-R1BJGim6rQUl_s>
Subject: Re: [Doh] POST and GET
X-BeenThere: doh@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DNS Over HTTPS <doh.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/doh>, <mailto:doh-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/doh/>
List-Post: <mailto:doh@ietf.org>
List-Help: <mailto:doh-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/doh>, <mailto:doh-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Sep 2018 06:18:19 -0000
On Tue, 18 Sep 2018, Sebastiaan Deckers wrote: > I have *implemented* both GET and POST code paths. But do they need to > exposed in every use case? I want to be able to support GET only for server > push, for example, and otherwise restrict client requests to POST. I presume a push should be sent to the client as a GET so that the client gets the full request that the response is going to respond to. > GET requires much more processing from a DOH proxy. I.e. parse the DNS > response packet to find the lowest TTL for HTTP cache-control header > max-age. As an operator I may want to disable support for GET requests from > the client and return 405 or 501. That wouldn't be compliant with the spec. -- / daniel.haxx.se
- [Doh] POST and GET Sebastiaan Deckers
- Re: [Doh] POST and GET bert hubert
- Re: [Doh] POST and GET Daniel Stenberg
- Re: [Doh] POST and GET Ben Schwartz