coolaj86/greenlock.js-ARCHIVED
3
3
Fork 0
Code Issues 6 Pull Requests 1 Releases Activity

ACME-v2: Invalid HTTP method when fething challenges #53

New Issue
Open
opened 2020-10-14 16:35:03 +00:00 by Ghost · 2 comments
Ghost commented 2020-10-14 16:35:03 +00:00
Copy Link

RFC8555 states:

   To request authorization for an identifier, the client sends a POST
   request to the newAuthz resource specifying the identifier for which
   authorization is being requested.

acme-v2 version 1.8.6 uses GET

RFC8555 states: ``` To request authorization for an identifier, the client sends a POST request to the newAuthz resource specifying the identifier for which authorization is being requested. ``` acme-v2 version 1.8.6 uses `GET`
coolaj86 commented 2020-10-14 18:09:29 +00:00
Owner
Copy Link

this was fixed over a year ago. you need to update to the latest version of greenlock.

this was fixed over a year ago. you need to update to the latest version of greenlock.
Ghost commented 2020-10-20 06:34:51 +00:00
Author
Copy Link

I've installed the latest version of greenlock-cli, which comes with acme-v2 1.8.6. I've used the following command:

npm install greenlock-cli

How can I update this to the compliant version?

I've installed the latest version of greenlock-cli, which comes with acme-v2 1.8.6. I've used the following command: ``` npm install greenlock-cli ``` How can I update this to the compliant version?
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Assignees
Clear assignees
jshaver coolaj86
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coolaj86/greenlock.js-ARCHIVED#53
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?