At home behind my router I have a raspberry pi that catch https traffic and serves an app in https on a domain with caddy (it’s working perfectly).
Now I would like to add another server in my network that serves https apps too on other domains.
I want my caddy to continue to serve app1 and to forward the rest of the https traffic to the other server so I tried to add a “catch-all :443 route” at the end of the caddyfile of my raspberry:
When I run caddy -port 443 browse and Caddy outputs:
Activating privacy features... done.
https://
My expectation from that result is that Caddy serves HTTPS on the default port, not that Caddy serves HTTP on port 443. I’d expect to see http://:443 instead in the latter case.
The problem isn’t that Caddy disables HTTPS, it’s that Caddy outputs https:// as the hostname regardless of that fact. It’s not https://, it’s http://:443. The initial output is effectively lying about the scheme it’s listening for.