mirror of
https://github.com/caddyserver/caddy.git
synced 2024-12-23 22:27:38 -05:00
8e75ae2495
If another ACME client is trying to solve a challenge for a name not being served by Caddy on the same machine where Caddy is running, the HTTP challenge will be consumed by Caddy rather than allowing the owner to use the Caddyfile to proxy the challenge. With this change, we only consume requests for HTTP challenges for hostnames that we recognize. Before doing the challenge, we add the name to a set, and when seeing if we should proxy the challenge, we first check the path of course to see if it is an HTTP challenge; if it is, we then check that set to see if the hostname is in the set. Only if it is, do we consume it. Otherwise, the request is treated like any other, allowing the owner to configure a proxy for such requests to another ACME client. |
||
|---|---|---|
| .. | ||
| storagetest | ||
| certificates.go | ||
| certificates_test.go | ||
| client.go | ||
| client_test.go | ||
| config.go | ||
| config_test.go | ||
| crypto.go | ||
| crypto_test.go | ||
| filestorage.go | ||
| filestorage_test.go | ||
| handshake.go | ||
| handshake_test.go | ||
| httphandler.go | ||
| httphandler_test.go | ||
| maintain.go | ||
| setup.go | ||
| setup_test.go | ||
| storage.go | ||
| tls.go | ||
| tls_test.go | ||
| user.go | ||
| user_test.go | ||