I tried to sign up via Google OAuth, but got the following error. Might this be an issue with the login mechanism?
Yeah, howâd you get the new domain name? 
Gimme another day or two to get all the properties transferred over.
Ah nevermind, I just went ahead and did the switch. Youâll have to log in again, sorry about that. But let me know if anything doesnât work!
Works like a charm now, thank you 
By the way, I really like this forum software. Although the community forum is not served by Caddy 
howâd you get the new domain name?
You posted it on Twitter 
Great! Yeah, I like Discourse.
It actually is I wrote up this example after fronting Discourse with Caddy: examples/discourse at master ¡ caddyserver/examples ¡ GitHub
Well, ok. I was confused by the server: nginx header in the responses.
Caddy proxies into a Docker container that the software ships in, and inside that container, nginx serves Discourse which is in Ruby I believe.
Caddyâs auto-HTTPS just makes it so much easier to do this way.
That is strange that the server header doesnât show Caddy too. It used toâŚ
1 Like
Is Caddy deferring to the upstream {>server} instead of adding its own maybe?
Iâm not sure, I havenât had a chance to look into it. I donât see anywhere in the code (at quick âFindâ glance) where the âServerâ header would be removed. It sets it one of the first things in httpserver/server.go. Iâll have to investigate further (or someone else can if they want to).
Iâm sure I remember a PR that changed a proxy from showing âcaddyâ as the server to transparently showing the proxied server.
Canât find it now though.