> I'm not certain, but in cases where acme spec is talking about the
> acme server acting as an http client, I'd request that `server` not be
> used bare.
> The easiest solution imo is labeling `acme-server` and
> `{http(s)}-server` / similar. But I'm open to other proposals.Agreed - I think this is a sensible change to reduce confusion. "ACME server" and "HTTP challenge server" seem like good choices but I'm also not tied to anything. >> 3. Dereference the URI using an HTTP GET request. This request MUST be sent >> to TCP port 80 on the server. >I think server here is http-server +1 >> 4. Verify that the body of the response is well-formed key authorization. The >> server SHOULD ignore whitespace characters at the end of the body. > I think here server is acme-server +1 >> 5. Verify that key authorization provided by the server matches the token for this challenge and the client's account key. > I think here server is acme-server I think this one should be "Verify that the key authorization provided by the HTTP challenge server", not the acme-server (or I need more coffee/cleaner glasses). Are you going to send a PR for this? If you're tied up with your existing PRs I will find a pinch hitter. - cpu On Tue, Feb 21, 2017 at 11:07 PM, Josh Soref <[email protected]> wrote: > https://github.com/ietf-wg-acme/acme/blob/28295572ca191cd14d6a9a21912b8d > 03aa65b885/draft-ietf-acme-acme.md#http > > > 3. Dereference the URI using an HTTP GET request. This request MUST be > sent to TCP port 80 on the server. > > I think server here is http-server > > > 4. Verify that the body of the response is well-formed key > authorization. The server SHOULD ignore whitespace characters at the end of > the body. > > I think here server is acme-server > > > 5. Verify that key authorization provided by the server matches the > token for this challenge and the client's account key. > > I think here server is acme-server > > > I'm not certain, but in cases where acme spec is talking about the > acme server acting as an http client, I'd request that `server` not be > used bare. > The easiest solution imo is labeling `acme-server` and > `{http(s)}-server` / similar. But I'm open to other proposals. > > _______________________________________________ > Acme mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/acme >
_______________________________________________ Acme mailing list [email protected] https://www.ietf.org/mailman/listinfo/acme
