Re: [Doh] handling HTTP re-directs in DoH
"Paul Hoffman" <paul.hoffman@vpnc.org> Fri, 12 April 2019 14:54 UTC
Return-Path: <paul.hoffman@vpnc.org>
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 E5DF01207D7
for <doh@ietfa.amsl.com>; Fri, 12 Apr 2019 07:54:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5
tests=[BAYES_00=-1.9] 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 t9-D1tneJLUu for <doh@ietfa.amsl.com>;
Fri, 12 Apr 2019 07:54:43 -0700 (PDT)
Received: from mail.proper.com (Opus1.Proper.COM [207.182.41.91])
(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 D752112006F
for <doh@ietf.org>; Fri, 12 Apr 2019 07:54:42 -0700 (PDT)
Received: from [10.32.60.122] (50-1-99-176.dsl.dynamic.fusionbroadband.com
[50.1.99.176]) (authenticated bits=0)
by mail.proper.com (8.15.2/8.15.2) with ESMTPSA id x3CEqnD7074344
(version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
Fri, 12 Apr 2019 07:52:50 -0700 (MST)
(envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: mail.proper.com: Host
50-1-99-176.dsl.dynamic.fusionbroadband.com [50.1.99.176] claimed to be
[10.32.60.122]
From: "Paul Hoffman" <paul.hoffman@vpnc.org>
To: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
Cc: doh@ietf.org
Date: Fri, 12 Apr 2019 07:54:32 -0700
X-Mailer: MailMate (1.12.4r5594)
Message-ID: <7B1712E7-114A-431E-809F-DCD612627FB8@vpnc.org>
In-Reply-To: <925aa4c9-d28d-d4b3-1461-2dfb17f40fac@cs.tcd.ie>
References: <925aa4c9-d28d-d4b3-1461-2dfb17f40fac@cs.tcd.ie>
MIME-Version: 1.0
Content-Type: text/plain; format=flowed
Archived-At: <https://mailarchive.ietf.org/arch/msg/doh/XR0IyvLCo82tp3cc0EprfagE_rQ>
Subject: Re: [Doh] handling HTTP re-directs in DoH
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: Fri, 12 Apr 2019 14:54:44 -0000
On 12 Apr 2019, at 4:39, Stephen Farrell wrote: > Discussion on another list prompted me to re-read 8484 to > see if I can understand what's supposed to happen if a DoH > server returns a 3xx. I didn't find an explicit answer in > the RFC, so am wondering what implementers do in that case? DoH is HTTPS. A DoH client is an HTTPS client. Redirects, caching, everything is plain HTTP and TLS. --Paul Hoffman
- [Doh] handling HTTP re-directs in DoH Stephen Farrell
- Re: [Doh] handling HTTP re-directs in DoH Daniel Stenberg
- Re: [Doh] handling HTTP re-directs in DoH Paul Hoffman
- Re: [Doh] handling HTTP re-directs in DoH Stephen Farrell