Re: [Acme] Content-Type and file extensions for HTTP01 challenges
Niklas Keller <me@kelunik.com> Wed, 18 November 2015 16:52 UTC
Return-Path: <me@kelunik.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A28681A8734 for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 08:52:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.027
X-Spam-Level:
X-Spam-Status: No, score=-1.027 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001] autolearn=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 NJZsgNIOyrnR for <acme@ietfa.amsl.com>; Wed, 18 Nov 2015 08:51:59 -0800 (PST)
Received: from mo6-p00-ob.smtp.rzone.de (mo6-p00-ob.smtp.rzone.de [IPv6:2a01:238:20a:202:5300::4]) (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 904201A872D for <acme@ietf.org>; Wed, 18 Nov 2015 08:51:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1447865515; l=435; s=domk; d=kelunik.com; h=Content-Type:Cc:To:From:Subject:Date:References:In-Reply-To: MIME-Version; bh=Q8XrX7Hclh0pK+od5VQG9vgn9C0sHNLVyNRVbTkap5s=; b=rAXUdLlfBYf0XddQRCOHlAPItNrhgzQTWrq0ap/cMMSKpZSWJ5XDJwiWBg92FSoDfPE RxKxu2tN+LxAe9y8XvLeDjEzpdKp6DFcwQXTgFJnfiz7L3AIJUO40BXL3erlpJfhVlxnC 1ESEqrUeGLcVUKRNTvk+zzWDpVsglJHEWkg=
X-RZG-AUTH: :IWkkfkWkbvHsXQGmRYmUo9mls2vWuiu+7SLGvomb4bl9EfHtOnM6
X-RZG-CLASS-ID: mo00
Received: from mail-wm0-f50.google.com ([74.125.82.50]) by smtp.strato.de (RZmta 37.14 AUTH) with ESMTPSA id 603d34rAIGptEIQ (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (curve secp384r1 with 384 ECDH bits, eq. 7680 bits RSA)) (Client did not present a certificate) for <acme@ietf.org>; Wed, 18 Nov 2015 17:51:55 +0100 (CET)
Received: by wmec201 with SMTP id c201so81970932wme.1 for <acme@ietf.org>; Wed, 18 Nov 2015 08:51:55 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.28.226.11 with SMTP id z11mr5452590wmg.56.1447865515272; Wed, 18 Nov 2015 08:51:55 -0800 (PST)
Received: by 10.194.2.171 with HTTP; Wed, 18 Nov 2015 08:51:55 -0800 (PST)
In-Reply-To: <CAHw9_iJwqqhMb+7+aj6Sszfi6_K9=rREEK3dbpQ6yddrmHSKsg@mail.gmail.com>
References: <20151113004436.GB18430@eff.org> <CABkgnnU5EzaPA4o7OgnTBpSQCZxjD+QsSV=4_L2rOBeFAoauKA@mail.gmail.com> <20151113011259.GC18430@eff.org> <1F85B447-6C45-4E5A-BB10-F1AD5CB2C3F3@vigilsec.com> <CABsBmKM9t3dX0_zq-EwsTOo7HpeMF6meiw9PhBaQLbHOCpGVGg@mail.gmail.com> <CAHw9_iJwqqhMb+7+aj6Sszfi6_K9=rREEK3dbpQ6yddrmHSKsg@mail.gmail.com>
Date: Wed, 18 Nov 2015 17:51:55 +0100
X-Gmail-Original-Message-ID: <CANUQDCgDeaLtaNfeEUQ3D=7EOwjL-Q0i6Q1FKxMTVtfY9d-bow@mail.gmail.com>
Message-ID: <CANUQDCgDeaLtaNfeEUQ3D=7EOwjL-Q0i6Q1FKxMTVtfY9d-bow@mail.gmail.com>
From: Niklas Keller <me@kelunik.com>
To: Warren Kumari <warren@kumari.net>
Content-Type: multipart/alternative; boundary="001a114b0e02b87d300524d375a9"
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/0Ri58i5qJE73WpXBZ0kcHwSbpDs>
Cc: IETF ACME <acme@ietf.org>, Russ Housley <housley@vigilsec.com>, Bryan Livingston <bryanlivingston@gmail.com>
Subject: Re: [Acme] Content-Type and file extensions for HTTP01 challenges
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Nov 2015 16:52:00 -0000
+1 for .txt, there are servers configured to serve only specific file extensions. Regards, Niklas
- [Acme] Content-Type and file extensions for HTTP0… Peter Eckersley
- Re: [Acme] Content-Type and file extensions for H… Richard Barnes
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Richard Barnes
- Re: [Acme] Content-Type and file extensions for H… Martin Thomson
- Re: [Acme] Content-Type and file extensions for H… Peter Eckersley
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Richard Barnes
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Russ Housley
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Salz, Rich
- Re: [Acme] Content-Type and file extensions for H… Warren Kumari
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Peter Eckersley
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Ted Hardie
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Martin Thomson
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Salz, Rich
- Re: [Acme] Content-Type and file extensions for H… Niklas Keller
- Re: [Acme] Content-Type and file extensions for H… Salz, Rich
- Re: [Acme] Content-Type and file extensions for H… Bryan Livingston