synchrone
commented
8 years ago Okay, since Radicale is set up under /radicale subpath - there is no way it's own /.well-known feature will work, so the nginx workaround is quite appropriate.
The only question is whether it really works
Radicale seems to be doing it's own .well-known support. The nginx config here tries to do such by itself, probably failing in the process.
Need to untangle this and probably remove nginx redirect.