https://bugs.freedesktop.org/show_bug.cgi?id=56240
Tobias Mueller <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |NOTABUG --- Comment #11 from Tobias Mueller <[email protected]> --- Okay. I found the problem. It's me. All is my fault. The "domain" key in the response header is wrongly used by me. neon is very correct about its semantics. The log said: "auth: Using domain /calendar from calendar". neon doesn't like that (cf http://svn.webdav.org/repos/projects/neon/trunk/src/ne_auth.c): /* Do not submit credentials if an auth domain is defined and this * request-uri fails outside it. */ if (sess->ndomains && !inside_domain(sess, req->uri)) { return NULL; } where sess->domains was filled with the values of the "domain" key in the response header. Neon didn't say that it was stopping the authentication because of that domain though... Interestingly, wget, curl, firefox, probably every HTTP client I tried, weren't as strict as neon. I think neon is right though after having read http://www.ietf.org/rfc/rfc2617.txt more closely especially on those weird values that nobody uses anyway ;-) The other clients are also right, because the RFC reads, they "can" respect that value. I don't know how I managed to configure Apache to send that key. Again: My bad. Next beer is on me. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
_______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
