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

Enable WFE2 "EnforceV2ContentType" flag in config-next. (#3562) 

We shipped this feature flag disabled because at the time Certbot's acme
module had a bug with revocation that sent the wrong content-type. That
has been fixed upstream and the current boulder-tools image has the fix.
We should be able to turn this flag on now for config-next without
breaking tests.
This commit is contained in:
Daniel McCarney 2018-03-14 16:09:58 -04:00 committed by GitHub
parent e00ed50cc3
commit 5172f03865
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
test/config-next/wfe2.json
View File

@ -32,7 +32,9 @@
"http://boulder:4430/acme/issuer-cert": [ "test/test-ca2.pem" ],
"http://127.0.0.1:4000/acme/issuer-cert": [ "test/test-ca2.pem" ]
},
"features": {}
"features": {
"EnforceV2ContentType": true
}
},
"syslog": {