http://bugzilla.moblin.org/show_bug.cgi?id=8758
--- Comment #4 from Chen Congwu <congwu.chen(a)intel.com> 2009-12-20 19:04:10 PST
---
(In reply to comment #0)
I was trying to break syncevolution and the UI with interesting
configs...
Setting syncURL to a http server that is not a syncml server gives a 405
response. Syncevolution then proceeds with the resend cycle. This seems
unnecessary and makes the user experience pretty bad: it takes 5 minutes to
find out that there's something wrong with the URL.
It's not easy to
differentiate between a temporary server error and a
non-SyncML server URL. ('405' means the http server do not support 'POST'
on
this URL, it does not necessarily mean: 1) the server is not a SyncML server
(might be a temporary error) 2) a non-SyncML server will always return this
error code as you commented in #2.
I will do the following:
As a first step, any name resolution and bad url error will not trigger resend.
Any non 200 HTTP response code for the *first* SyncML request (in a session)
will not trigger resend.
I should maybe file a new bug for this but maybe this is related: I get 20043
(LOCERR_TRANSPFAIL) as the eventual error for the above. That is the exact same
thing I get for failed name resolution (syncURL="http://invalid.invalid") and
a
bad url (syncURL="a"). Being able to tell those apart would be great.
--
Configure bugmail:
http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.