certificates/acme/api
Clive Jevons 639993bd09 Read host and protocol information from request for links
When constructing links we want to read the required host and protocol
information in a dynamic manner from the request for constructing ACME
links such as the directory information. This way, if the server is
running behind a proxy, and we don't know what the exposed URL should
be at runtime, we can construct the required information from the
host, tls and X-Forwarded-Proto fields in the HTTP request.
Inspired by the LetsEncrypt Boulder project (web/relative.go).
2020-05-12 16:58:12 -07:00
..
account.go ACME accountUpdate ignore fields not recognized by the server. 2020-05-08 11:52:30 -07:00
account_test.go ACME accountUpdate ignore fields not recognized by the server. 2020-05-08 11:52:30 -07:00
handler.go Read host and protocol information from request for links 2020-05-12 16:58:12 -07:00
handler_test.go Read host and protocol information from request for links 2020-05-12 16:58:12 -07:00
hostutil.go Read host and protocol information from request for links 2020-05-12 16:58:12 -07:00
hostutil_test.go Read host and protocol information from request for links 2020-05-12 16:58:12 -07:00
middleware.go Add x5c provisioner capabilities 2019-10-14 14:51:37 -07:00
middleware_test.go Should be returning status code 400 for ACME Account Not Found. 2020-02-01 17:35:41 -08:00
order.go Add x5c provisioner capabilities 2019-10-14 14:51:37 -07:00
order_test.go Should be returning status code 400 for ACME Account Not Found. 2020-02-01 17:35:41 -08:00