Breaking changes are coming on March 29th, 2018 in ACMEv2 #1

New Issue

Ghost · 2018-03-15T07:47:23Z

Ghost commented

2018-03-15 07:47:23 +00:00

Hey AJ,

I just saw you started to work on that, this is awesome! I was wondering something:

As stated here, there will be breaking changes in ACMEv2 on March 29th, 2018. Will they be handled accordingly?

Thanks,

Hey AJ, I just saw you started to work on that, this is awesome! I was wondering something: As stated [here](https://community.letsencrypt.org/t/jws-post-content-type-header-enforcement/55055), there will be breaking changes in ACMEv2 on March 29th, 2018. Will they be handled accordingly? Thanks,

coolaj86 commented

2018-03-15 16:56:35 +00:00

Yes, I am using Content-Type: application/jose+json.

Thanks for bringing it to my attention. :)

Yes, I am using `Content-Type: application/jose+json`. Thanks for bringing it to my attention. :)

coolaj86 closed this issue

2018-03-15 16:56:35 +00:00

coolaj86 commented

2018-03-20 07:28:54 +00:00

I got my first hard-coded test working end-to-end. :)

Sign in to join this conversation.

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coolaj86/acme.js-ARCHIVED#1