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

Richard Barnes <rlb@ipv.sx> Fri, 31 August 2018 17:21 UTC

Return-Path: <rlb@ipv.sx>
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 7B361128CFD for <acme@ietfa.amsl.com>; Fri, 31 Aug 2018 10:21:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level:
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.com
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 YhdRkKcf7ImR for <acme@ietfa.amsl.com>; Fri, 31 Aug 2018 10:21:49 -0700 (PDT)
Received: from mail-oi0-x22c.google.com (mail-oi0-x22c.google.com [IPv6:2607:f8b0:4003:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DA341277CC for <acme@ietf.org>; Fri, 31 Aug 2018 10:21:49 -0700 (PDT)
Received: by mail-oi0-x22c.google.com with SMTP id l202-v6so22960441oig.7 for <acme@ietf.org>; Fri, 31 Aug 2018 10:21:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=C/xEE58NjdjvRjAuFydqWoUtKSXlOt0t2IsulOYpWCg=; b=eUcgaF8A2HmHHCSR9ioOlAZXwCXAvQ7FmGjERjIbQ4MGLVMcOFkKB69ovT3SxyqWWM wK3+0ZicPT7kvAaGBoapo5RLTpPW6dF/rakkRITgTEXBfPHJaDlOYXZj4Sk8MixpnVh9 ln3gv/4O2gtj5yMJVXo1OCm+rTMMy8rSU8NdUsV8dseXatqUh7Sh2IFy1FgTfAC/9hv3 46X9FQjsyafheXTLT67YmqnHbYvgwWW8IacnM+Lq07zRR3Aa6lgb31BK4b4JGN6wC9VI 3o3jvOIQ2/+3Ui292PPygJygXc7jY/KunCWp2q6Z/sdCisa3B4i/Hs4P3mk7T60Kmx7y hhtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=C/xEE58NjdjvRjAuFydqWoUtKSXlOt0t2IsulOYpWCg=; b=N2GdSGQ83P1I6VV/BRHFeTefVA8J/leQJXEadY9UHW2XAg0y9Mq5ji9bqRBGoKxL5S OYQHc0w+PjocZuIkWn+sE9SnbxvAtEeWIP4mVIuFyI+VuRlOEpiFkC/iEAB74xuv9sx7 zIe7qFBhUBOYGiv/fBFi5AUGPpEIjiLIOihfw2ZV4B6DhuaRhLIVfPX92RgDlXqDa873 IjqLhPebBJKjIJTtJ0vwQeQYETN5idReuGZ+oG0XH8tonZGoNNCKxjhzB8g8WLQKsAkh p60VXpFq1Wx7F1vohyTuuhHvbDQgL9syTPAVvIlHPPNXT+iAKfMR7dnOxaEygxuVHrP7 3PAg==
X-Gm-Message-State: APzg51A4x7esOwHo1W90bpJmfEMhRhrIil1O5d9cQKuU+kj2ptbNobn5 BA8uJqSTJ/i8DoRA++FfLYE+I0DecWQDBmBcWlZ6Qg==
X-Google-Smtp-Source: ANB0VdYN+faKl9SnMOMu+F3p1EEjd2kCHTHxQWKmdn0clrfABkzQ9bJ6lg6sTjiIgUwT79333qPW1g46slWpeo6nBBw=
X-Received: by 2002:aca:fd4f:: with SMTP id b76-v6mr8667436oii.307.1535736107111; Fri, 31 Aug 2018 10:21:47 -0700 (PDT)
MIME-Version: 1.0
References: <c33184f3-4e64-b7ea-babb-d29e2307f1f3@eff.org> <CAL02cgRD=UgsaDeWN9hy2YXN=CLLQpt+zgaZKPTqDpoiMi0hqw@mail.gmail.com> <863A4A5E-718A-4C29-AE82-097C70BE75B6@akamai.com>
In-Reply-To: <863A4A5E-718A-4C29-AE82-097C70BE75B6@akamai.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Fri, 31 Aug 2018 13:21:35 -0400
Message-ID: <CAL02cgQ=FjSLYuzKMnkbVHqPaU7A1sc5xSCk6dWa67=1a3b3vw@mail.gmail.com>
To: "Salz, Rich" <rsalz@akamai.com>
Cc: Jacob Hoffman-Andrews <jsha@eff.org>, IETF ACME <acme@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000222a350574be6d51"
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/xGRhSuEVfW3VBKukOL8m86BGJMI>
Subject: Re: [Acme] ACME breaking change: Most GETs become POSTs
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 31 Aug 2018 17:21:52 -0000

No, if a server receives a GET request for a resource other than those
specified, then it MUST return 405.  But please check out the PR and see if
it's clear there.

On Fri, Aug 31, 2018 at 1:14 PM Salz, Rich <rsalz@akamai.com> wrote:

>
>    - * Servers MUST return a 405 if they get a GET for a resource other
>    than directory/newNonce/certificate.
>
>
>
> They means client? Or there’s a word missing, and “they get a” is “they do
> not support”
>