On Mon, 2013-11-25 at 10:55 +0100, Patrick Ohly wrote: > On Sun, 2013-11-24 at 12:06 +0100, Thomas Pequet wrote: > > Le 23/11/2013 20:12, Patrick Ohly a écrit : > > > On Fri, 2013-11-22 at 15:18 +0100, Patrick Ohly wrote: > > >> On Fr, 2013-11-22 at 09:35 +0100, Thomas Pequet wrote: > > >>> Le 21/11/2013 20:39, Patrick Ohly a écrit : > > >>>> On Do, 2013-11-21 at 18:14 +0100, Thomas Pequet wrote: > > >>>>> Le 21/11/2013 17:32, Patrick Ohly a écrit : > > >>>>> > > >>>>>> On Do, 2013-11-21 at 17:10 +0100, Thomas Pequet wrote: > > >>>>>>> Do you use IPv6 ? > > >>>>>> Could be. At least the machine and the transparent proxy it sits > > >>>>>> behind > > >>>>>> are IPv6 enabled. I'm less sure whether libsoup uses IPv6. > > >>>>> Ok I havejust change the IPv6 so I think it is that. > > >>>>> Can you try again ? > > >>>> Still fails. > > >>>> > > >>>> Note to self: a simple test is "curl http://www.memotoo.com/syncmldev"; > > >>> Can you try again ? > > >> Now it seems to work, at least with curl. Still need to run SyncML > > >> tests. > > > Now it seems to be broken again. > > > > > Very strange ... > > It seems the failure is not perfectly deterministic. It now failed once, > worked the next second, then failed again.
Perhaps it's also a load issue. $ time curl -v http://www.memotoo.com/syncmldev [eventually the redirect is returned] real 2m1.055s user 0m0.008s sys 0m0.000s 2 minutes for a single request? It's not surprising that there are timeouts, most likely in the HTTP proxy. -- 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] https://lists.syncevolution.org/mailman/listinfo/syncevolution
