https://bugs.kde.org/show_bug.cgi?id=344874
--- Comment #9 from Olaf Titz <o...@bigred.inka.de> --- There is a recurring issue in support fora related to owncloud and iOS/Android CalDAV sync apps. I still don't understand it completely, but it seems to be related to two or three potential reasons. All of them have to do with the fact that PROPFIND is treated differently from GET (at least by Apache). 1. Sure: a number of misconfigurations of Apache can cause Apache and/or Owncloud to misunderstand the initial PROPFIND request. There is plenty of documentation about that. (Everything here applies not to owncloud exclusively but to all Apache/PHP-based DAV services.) 2. Confirmed: When the requested resource is not known (wrong URL), Apache responds 405 instead of 404 to PROPFIND, so the end user gets a misleading technical error message instead of a plain "URL not found". 3. Speculative: it looks like Apache responds 405 instead of 401 too in certain circumstances, but I'm not exactly sure what causes this. This is what really can cause breakage to the authorization protocol. The DAVdroid app has an option to always send an Authorization header with the first request to work around these kind of problems (at least the #3 one) and the recommendation could be that Akonadi get such an option too. (Now I don't have the problem any more since I fixed my setup on all three sides (owncloud, android, akonadi) but getting it right everywhere was much harder than it should be...) -- You are receiving this mail because: You are watching all bug changes.