meego-dev@meego.com
> Subject: RE: [MeeGo-dev] Trying to sync Buteo with Google
>
> Hi Patrick and Yongsheng,
>
> I found the root cause here. So the post was going to the redirected URI, that
> wasn't the issue. The respURI sent to us by Google was percent encoded and
&g
esh (Nokia-MS/Bangalore); meego-dev@meego.com
>Subject: Re: [MeeGo-dev] Trying to sync Buteo with Google
>
>On Thu, 2010-10-14 at 09:28 +0100, Zhu, Yongsheng wrote:
>> > Deepak said that Buteo does not follow the redirect that
>it gets in
>> > the first response from th
On Thu, 2010-10-14 at 09:28 +0100, Zhu, Yongsheng wrote:
> > Deepak said that Buteo does not follow the redirect that it gets in the
> > first response from the SyncML server. This redirect is part of the
> > SyncML protocol; if Deepak is right, then this is the root cause of the
> > problem and ne
> Deepak said that Buteo does not follow the redirect that it gets in the
> first response from the SyncML server. This redirect is part of the
> SyncML protocol; if Deepak is right, then this is the root cause of the
> problem and needs to be fixed.
You mean respURI in the 'response' syncml messag
On Thu, 2010-10-14 at 04:20 +0100, Zhu, Yongsheng wrote:
> As a workaround, I put cred information each time Buteo sends
> xyncml message to Google. Now it syncs!
Have you verified which URL is used in each POST?
Deepak said that Buteo does not follow the redirect that it gets in the
first respon
As a workaround, I put cred information each time Buteo sends
xyncml message to Google. Now it syncs!
Cheers,
Yongsheng
> -Original Message-
> From: Ohly, Patrick
> Sent: Wednesday, October 13, 2010 5:41 PM
> To: Zhu, Yongsheng
> Cc: Sateesh Kavuri; meego-dev@meego.com
> Subject: RE: Try
Previously I used non-https protocol, but failed.
Cheers,
Yongsheng
> -Original Message-
> From: Ohly, Patrick
> Sent: Wednesday, October 13, 2010 5:41 PM
> To: Zhu, Yongsheng
> Cc: Sateesh Kavuri; meego-dev@meego.com
> Subject: RE: Trying to sync Buteo with Google
>
> On Wed, 2010-10-1
Hi,
>-Original Message-
>From: meego-dev-boun...@meego.com
>[mailto:meego-dev-boun...@meego.com] On Behalf Of ext Patrick Ohly
>Sent: Wednesday, October 13, 2010 2:59 PM
>To: Zhu, Yongsheng
>Cc: Kavuri Sateesh (Nokia-MS/Bangalore); meego-dev@meego.com
>Subject: Re:
On Wed, 2010-10-13 at 10:32 +0100, Zhu, Yongsheng wrote:
> > the HTTP POST from Buteo going to the redirected URL?
> Yes, previously it is failed in http error '404'.
"previous" to what? Did you have to modify the URL handling in order to
get to the current point?
--
Best Regards, Patrick Ohly
> Indeed, no apparent relevant difference stands out. Perhaps there is
> some difference outside of the message content itself?
Maybe.
> Do both programs
> use the same message encoding (should be WBXML for SyncEvolution)?
Yes, because Google only supports WBXML.
> the HTTP POST from Buteo going t
On Wed, 2010-10-13 at 09:42 +0100, Zhu, Yongsheng wrote:
> Hi, Sateesh & Patrick
> I'm working on trying to sync Buteo with Google service via SyncML protocol.
> Currently it's blocked
> because Google service sends 'unauthorized' error. See the attached syncML
> messages "buteo-msgs.zip".
> Sinc
11 matches
Mail list logo
