Commit Graph
2 Commits
Author SHA1 Message Date
Tejas ChopraandClaude Opus 5.5 ac0e596ffb fix(docker): let the HTTPS compose serve /v1/compress to callers through Caddy
Caddy reaches Headroom from a container-network address, and the
compression endpoints (/v1/compress, /v1/usage) accept only local
callers unless HEADROOM_COMPRESS_ALLOW_REMOTE is set, so every remote
client got 404 even with the proxy token. The compose file now sets it;
the proxy token still authenticates every request.

Assay-Kind: bugfix
Assay-Ask: Remote clients calling /v1/compress through the HTTPS compose setup got 404 despite presenting the proxy token.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-13 14:02:04 -08:00
Tejas ChopraandClaude Opus 5.5 c80cb94930 feat(docker): add a compose file that serves a shared proxy over HTTPS with Caddy
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>
2026-11-13 12:36:59 -08:00