From 5172f0386598fbc88be9dfaf21ce720235eecbc7 Mon Sep 17 00:00:00 2001 From: Daniel McCarney Date: Wed, 14 Mar 2018 16:09:58 -0400 Subject: [PATCH] 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. --- test/config-next/wfe2.json | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/test/config-next/wfe2.json b/test/config-next/wfe2.json index e06581b4f..e54d601a9 100644 --- a/test/config-next/wfe2.json +++ b/test/config-next/wfe2.json @@ -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": {