forked from TrueCloudLab/certificates
639993bd09
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). |
||
|---|---|---|
| .. | ||
| api | ||
| account.go | ||
| account_test.go | ||
| authority.go | ||
| authority_test.go | ||
| authz.go | ||
| authz_test.go | ||
| certificate.go | ||
| certificate_test.go | ||
| challenge.go | ||
| challenge_test.go | ||
| common.go | ||
| directory.go | ||
| directory_test.go | ||
| errors.go | ||
| nonce.go | ||
| nonce_test.go | ||
| order.go | ||
| order_test.go | ||