IETF Logo Mail Archive

Re: [Acme] ACME breaking change: Most GETs become POSTs

Alan Doherty <ietf@alandoherty.net> Mon, 10 September 2018 16:12 UTC

Return-Path: <ietf@alandoherty.net>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6F3A124BE5 for <acme@ietfa.amsl.com>; Mon, 10 Sep 2018 09:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level:
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FORGED_MUA_EUDORA=0.001, T_SPF_PERMERROR=0.01] autolearn=no 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 d-KzA35fg9au for <acme@ietfa.amsl.com>; Mon, 10 Sep 2018 09:12:43 -0700 (PDT)
Received: from bigsvr.orionnetworks.ie (hosting.orionnetworks.ie [195.2.202.63]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72842130E52 for <acme@ietf.org>; Mon, 10 Sep 2018 09:12:43 -0700 (PDT)
Received: from host249.freudenhaus.alandoherty.net ([193.120.128.249]:2137 helo=alans-p4.alandoherty.net) by bigsvr.orionnetworks.ie with esmtpsa(TLSv1:DHE-RSA-AES256-SHA:256) (auth-as tel1) (nexus 1.3.4.80.1) (envelope-from <ietf@alandoherty.net>) id 1fzOnk-0001Vk-0A ; Mon, 10 Sep 2018 16:12:41 +0000
X-AD-RPFS-HEAD: for info on below codes http://www.alandoherty.net/mailsystem/mail-tagging/
X-AD-RPFS-GOOD-0: AV-SCAN-PASS SA-SCORE--1.7 SA-BAR-(-)
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Mon, 10 Sep 2018 17:12:33 +0100
To: Erica Portnoy <erica@eff.org>
From: Alan Doherty <ietf@alandoherty.net>
Cc: acme@ietf.org
In-Reply-To: <41fda3f1-662f-4fd4-80f5-dc92053f7057@email.android.com>
References: <E1fzK7M-0000N2-J6@bigsvr.orionnetworks.ie> <41fda3f1-662f-4fd4-80f5-dc92053f7057@email.android.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <E1fzOnk-0001Vk-0A@bigsvr.orionnetworks.ie>
X-VIRUS: NONE {no virus found, This is no guarentee}
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/uHdQ-8-pTfbrBIKCWAcpDX0LEsA>
Subject: Re: [Acme] ACME breaking change: Most GETs become POSTs
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Sep 2018 16:12:45 -0000

At 16:03 10/09/2018  Monday, Erica Portnoy wrote:
>> I think you must have 
>> as all this discussion relates to traffic from acme-client to acme-server 
>> thus both https 
>> and obviously 1 known api/name 
>> 
>> you seem to be discussing traffic to an acme-customer's webserver 
>
>Yes, because the acme client and the client's web server are often the same exact server, and even when not, are often run on the same machine.

and the location of the acme-client alters the truth of the above how?

v2.23.0 | Report a Bug | By Email