boulder/wfe2
Jacob Hoffman-Andrews cf9df961ba
Add feature flags for upcoming deprecations (#6043)
This adds three features flags: SHA1CSRs, OldTLSOutbound, and
OldTLSInbound. Each controls the behavior of an upcoming deprecation
(except OldTLSInbound, which isn't yet scheduled for a deprecation
but will be soon). Note that these feature flags take advantage of
`features`' default values, so they can default to "true" (that is, each
of these features is enabled by default), and we set them to "false"
in the config JSON to turn them off when the time comes.

The unittest for OldTLSOutbound requires that `example.com` resolves
to 127.0.0.1. This is because there's logic in the VA that checks
that redirected-to hosts end in an IANA TLD. The unittest relies on
redirecting, and we can't use e.g. `localhost` in it because of that
TLD check, so we use example.com.

Fixes #6036 and #6037
2022-04-15 12:14:00 -07:00
..
test Fix various WFE2 bugs. (#3292) 2017-12-19 13:13:29 -08:00
README.md Duplicate WFE to WFE2. (#2839) 2017-07-05 13:32:45 -07:00
cache.go Add account cache to WFE (#5855) 2021-12-15 11:10:23 -08:00
cache_test.go Add account cache to WFE (#5855) 2021-12-15 11:10:23 -08:00
prod_aia.go Fixup staticcheck and stylecheck, and violations thereof (#5897) 2022-01-20 16:22:30 -08:00
stale.go Unwrap SA Get[Pre]Certificate methods (#5588) 2021-08-19 15:43:48 -07:00
stale_test.go GRPC: Unwrap ra.DeactivateAuthorization (#5567) 2021-08-12 11:30:57 -07:00
stats.go Switch away from old style statsd metrics wrappers (#4606) 2019-12-18 11:08:25 -05:00
test_aia.go Remove wfe1 integration tests (#5840) 2021-12-10 12:40:22 -08:00
verify.go Improve error checking paradigm (#5920) 2022-02-01 14:42:43 -07:00
verify_test.go Add account cache to WFE (#5855) 2021-12-15 11:10:23 -08:00
wfe.go Add feature flags for upcoming deprecations (#6043) 2022-04-15 12:14:00 -07:00
wfe_test.go Add feature flags for upcoming deprecations (#6043) 2022-04-15 12:14:00 -07:00

README.md

WFE v2

The wfe2 package is copied from the wfe package in order to implement the "ACME v2" API. This design choice was made to facilitate a clean separation between v1 and v2 code and to support running a separate API process on a different port alongside the v1 API process.