On Fr, 2011-02-25 at 17:19 +0000, Thomas Pequet wrote: > Hello Patrick > > Sorry for the delay ... > > The problem come may be from the user agent that have no > "SyncEvolution" value ...
That's a bit surprising, I don't know where that gets lost. I had already suspected that the proxy might be at fault, but couldn't reproduce that. > I have added an other test to determine if is SyncEvolution with > "syncevolution-" in "LocURI". You mean the device ID? Like "syncevolution-064acd33-f44a-4ba3-be1c-6d3f410e1493"? That's also problematic, because there's no guarantee that this user-configurable string really starts with "syncevolution-". A more reliable way would be to check the DevInf. I believe the server has the client's DevInf before it needs to send its own, at least with SyncEvolution+Synthesis. Anyway, it's good that the nightly tests should pass now. -- 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
