Closed alethiophile closed 2 years ago
Thanks for the detailed bug report :+1:. I don't use Caddy personally so I will need to take a look.
I believe I've fixed the issue. During my earlier experimentation I had somehow managed to get two different mango-sessid
cookies set on different paths, as you can see in the Caddy request transcript; this was messing up the login. Clearing those cookies made the problem go away.
Glad to know that you got it working!
Describe the bug Currently trying to set up Mango behind my existing reverse proxy, which runs Caddy. While Mango works fine if set up behind nginx, it fails under Caddy; after I try to log in, I just get a redirect back to the login page.
To Reproduce Steps to reproduce the behavior:
Environment (please complete the following information):
Additional context Watching the network traffic, the behavior of nginx and caddy are different in many ways. Caddy uses a single connection rather than reopening per request, preserves the client's upstream Host header, automatically sets various forwarding headers, and so forth. However, caddy is a standards-compliant reverse proxy that works with any other web app. Thus, it seems Mango should support Caddy as reverse proxy in its default configuration, or at least provide documentation about what other configuration options are necessary.
Attached is the request Caddy forwards to Mango on login:
By comparison, the nginx version, which works: