letsencrypt
/
boulder
mirror of https://github.com/letsencrypt/boulder.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Adds some divergences (#2578) 

Adds some draft-05 divergences RE: account status field, challenge status code.
This commit is contained in:
Sophie Herold 2017-02-27 15:36:17 +01:00 committed by Daniel McCarney
parent 9da55fd5a5
commit 5be390e9d7
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/acme-divergences.md
View File

@ -62,7 +62,9 @@ Boulder doesn't implement the `new-nonce` endpoint, instead it responds to `HEAD
Boulder only allows `mailto` URIs in the registrations `contact` list.
Boulder uses a HTTP status code 409 (Conflict) response for an already existing registration instead of 200 (OK). Boulder returns the URI of the already existing registration in a `Location` header field instead of a `Content-Location` header field.
Boulder uses an HTTP status code 409 (Conflict) response for an already existing registration instead of 200 (OK). Boulder returns the URI of the already existing registration in a `Location` header field instead of a `Content-Location` header field.
Boulder does not return the `status` field.
## [Section 6.3.3.](https://tools.ietf.org/html/draft-ietf-acme-acme-05#section-6.3.3)
@ -80,6 +82,8 @@ Boulder ignores the `existing` field in authorization request objects.
Boulder returns an `uri` instead of an `url` field in challenge objects.
Boulder uses an HTTP status code 202 (Accepted) response for correct challenge responses instead of 200 (OK) as defined in [Section 6.1](https://tools.ietf.org/html/draft-ietf-acme-acme-05#section-6.1).
## [Section 7.3.](https://tools.ietf.org/html/draft-ietf-acme-acme-05#section-7.3)
Boulder implements `tls-sni-01` from [draft-ietf-acme-01 Section 7.3](https://tools.ietf.org/html/draft-ietf-acme-acme-01#section-7.3) instead of the `tls-sni-02` validation method.