Headroom's listener speaks plain HTTP, so a shared proxy sent the proxy
token, prompts and provider credentials across the network unencrypted
unless the operator built their own HTTPS front. docker-compose.https.yml
runs Caddy in its own container in front of Headroom: Caddy serves HTTPS
and renews the certificate, Headroom's port stays on the compose network,
and the proxy token is required. Caddy reaches Headroom by service name,
not loopback, so the token is still checked on every request.
Assay-Kind: feature
Assay-Ask: Teams running Headroom as a shared proxy had no simple way to serve it over HTTPS.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>