Le lundi 12 octobre 2009 à 13:51 +0200, Andrzej Wąsowski a écrit :
Julien,
On Mon, 12 Oct 2009, Julien Garet wrote:
>> In my setup I was able to advance a bit by switching the requirement for
>> certificates off (I also was not able to get the certificates succeed, with
>> the same error as you do).
> Do you mean setting SSLVerifyServer = 0 and SSLVerifyHost = 0 ?
Yes, this is what I did (I tried to add the certificate by exporting it from
FireFox on the calendar website, but this did not work. Libsoup was
complaining).
> It does not work better for me.
Were you still getting the same error message? I start to wonder if I do not
suffer from the ssl problem myself, while I try to find the solution
elsewhere.
Yes, I am getting error messages from libsoups :
[INFO] SoupTransport Failure:
https://agenda.inria.fr:4444/ocst-bin/ocas.fcgi via libsoup: Connection
terminated unexpectedly
telnet agenda.inria.fr:4444 works well... There might be something the
client says to the server that is unpleasant...
I attach the sysynclib* files from the last run of syncevolution. I have
from where I run the syncevolution client a syncclient_sample_config.xml
containing various tests from the mails of the day.
> syncURL =
https://agenda.inria.fr:4444/ocst-bin/ocas.fcgi
> username = garet
> password = "<my_password>"
> logdir = /tmp/syncevo
> loglevel = 5
> maxlogdirs = 1
> RetryInterval = 5
> deviceId = sc-pim-290f49b4-ab78-4c7b-9c82-6bed35815f2c
> SSLVerifyServer = 0
> SSLVerifyHost = 0
> WebURL =
> IconURI =
> ConsumerReady = 1
>
> and here are my sources files :
> addressbook/config.ini:sync = none
> addressbook/config.ini:type = addressbook:text/vcard
> addressbook/config.ini:uri = ./Contacts
>
> calendar/config.ini:sync = two-way
> calendar/config.ini:type = calendar
> calendar/config.ini:uri = ./Calendar/Events
I only use the calendar at the moment - I want to make it work first. But my
set up is essentially the same as yours.
Other users of my server also add a query limitiing the scope of
synchronization. I heard rumours that unlimited does not work, but I do not
know if this is a client or a server limitation in their cases.
I think our server is set to do something like +60 days in the future,
does not know if it's default.
calendar/config.ini:uri = ./Calendar/Events?/dr(-60,180)
Gives a scope of 60 days back and 180 in future.
Andrzej