On Mo, 2011-05-23 at 11:08 +0100, Salvatore Iovene wrote: > If we're contacting a webdav server, trying to retrieve properties at an > address like https://example.com/dav/username/events, a likely reason for > a 404 error is that the username is invalid. We can't have a proper > heuristic to determine that, so let's just assume an authentication > error and inform the user accordingly.
Not merged. See my comments from the merge request: check_error(): not in line with function naming, use checkError() Translating the 404 error into 401 is too aggressive. It should only be done if the path for which the error was triggered really was the one where %u was substituted. Please rework these patches and commit as a new branch to the upstream repo. -- Best Regards, Patrick Ohly The content of this message is my personal opinion only and although I am an employee of Intel, the statements I make here in no way represent Intel's position on the issue, nor am I authorized to speak on behalf of Intel on this matter. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
