ACME directory URL redirects are not followed #75
Description
Bug Overview
When the configured acme_issuer uri points to a directory URL that returns an HTTP redirect (e.g., 301) to another path, the client does not follow the redirect. Instead, it attempts to directly deserialize the redirect response body as a JSON ACME directory object and fails with an error similar to:
directory update failed (cannot deserialize response (invalid type: null, expected a sequence at line 1 column 1)) while creating account for acme issuer "acme_config"
Example: uri https://acme.example.com/directory; redirects to https://acme.example.com/some-id/directory.
Expected Behavior
The module should support and follow redirects.
Steps to Reproduce the Bug
- Configure an issuer in NGINX that points to a redirecting directory URL
- Start or reload NGINX to trigger account creation.
- Observe the error in the error log (message as above) and no progress past directory fetch.
Environment Details
- Target deployment platform: Docker Image
- Target OS: Debian Trixie
- Version of this project or specific commit: v0.2.0
- Version of any relevant project languages: rustc 1.90.0
Additional Context
No response