IETF Logo Mail Archive

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

Erica Portnoy <erica@eff.org> Mon, 10 September 2018 15:04 UTC

Return-Path: <erica@eff.org>
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 B826B130E4F for <acme@ietfa.amsl.com>; Mon, 10 Sep 2018 08:04:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.723, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eff.org
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 ECLs345RNZ4P for <acme@ietfa.amsl.com>; Mon, 10 Sep 2018 08:04:03 -0700 (PDT)
Received: from mail2.eff.org (mail2.eff.org [173.239.79.204]) (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 9C5DB1277BB for <acme@ietf.org>; Mon, 10 Sep 2018 08:04:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=eff.org; s=mail2; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Cc:To:From: In-Reply-To:Message-ID:Subject:Date:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:References:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=0KPmDQaU7YwyPTpbUI99unVFbTO1VYSIc+FIFmyzkoc=; b=PF3mZFI+nqjWEJFhgmkZ9za0r/ uV/rfb+qsO6GI8ngbfMvASJa1alsED6HRsZMARdC9zXrHPaw4l+GhTcvohvJU1zEF8YYGCdwjE4C3 xT6DTXAVfdgxz7y/D9s5BJY7CFI5hQ7tndHlklkwktcECT0I1NWTR9ggJxAzBamNPFe8=;
Received: ; Mon, 10 Sep 2018 08:04:02 -0700
Date: Mon, 10 Sep 2018 08:03:57 -0700
Message-ID: <41fda3f1-662f-4fd4-80f5-dc92053f7057@email.android.com>
X-Android-Message-ID: <41fda3f1-662f-4fd4-80f5-dc92053f7057@email.android.com>
In-Reply-To: <E1fzK7M-0000N2-J6@bigsvr.orionnetworks.ie>
From: Erica Portnoy <erica@eff.org>
To: Alan Doherty <ietf@alandoherty.net>
Cc: acme@ietf.org
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/ScyboTv7DtxdJcW0jCezTCW1j5U>
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 15:04:05 -0000

> 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.

v2.23.0 | Report a Bug | By Email