Hello!
I just reinstalled DAVdroid and tried to use the new method with .well-known addresses. I am using OwnCloud 7, installed on a /ownlcoud/ subfolder, and the .htaccess file was changed accordingly. But I got the same HTTP 405 error as the bug reporter.
An excerpt from my example.com/owncloud/.htaccess:
RewriteEngine on RewriteRule .* - [env=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteRule ^\.well-known/host-meta /owncloud/public.php?service=host-meta [QSA,L] RewriteRule ^\.well-known/host-meta\.json /owncloud/public.php?service=host-meta-json [QSA,L] RewriteRule ^\.well-known/carddav /owncloud/remote.php/carddav/ [R] RewriteRule ^\.well-known/caldav /owncloud/remote.php/caldav/ [R]When calling the domain manually in a browser, something like example.com/owncloud/.well-known/carddav is redirected correctly to example.com/owncloud/remote.php/carddav. But it doesn’t work in DAVdroid. Please note that everything is done with https.
Maybe it has something to do with the first RewriteRule. I don’t know what it does, and since the manual request works, I did not investigate there further. But then I had an idea. What if DAVdroid really needs a server address without subdirectories?
I added the four lines with .well-known addresses to my .htaccess file in root folder (example.com/.htaccess), tried again: works! DAVdroid found my OwnCloud caldav and carddav addresses, everything fine. Afterwards you can remove these lines again.
So the question is, error on htaccess configuration or in DAVdroid?