Deepak, Great. Many thanks. I'll update it. Cheers, Yongsheng
> -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Thursday, October 14, 2010 4:51 PM > To: Ohly, Patrick; Zhu, Yongsheng > Cc: [email protected]; [email protected] > 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 > there was a bug in the stack in creation of QUrls from percent encoded URLs. > I fixed that and it works fine. Will be pushing the changes soon to > buteo-syncml. > > Regards, > Deepak > > >-----Original Message----- > >From: [email protected] > >[mailto:[email protected]] On Behalf Of ext Patrick Ohly > >Sent: Thursday, October 14, 2010 2:15 PM > >To: Zhu, Yongsheng > >Cc: Kavuri Sateesh (Nokia-MS/Bangalore); [email protected] > >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 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 message? I found > >it has been > >> used to send next message. > > > >Yes. So it already behaves as it should. Good. > > > >> > Sending credentials each time is merely a workaround and not one > >> > that we can rely on (Google might change their behavior > >for handling > >> > ensuing messages at the starting URL). > >> Yes, it should be a workaround to help us overcome this one. > > > >Fair enough. Note that there have been some authentication > >related changes recently in the upstream buteo-syncml repo. > >The commit messages don't say which server provided the > >motivation for these changes; perhaps they also help with Google. > > > >In the meantime, let's use your patch. > > > >-- > >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. > > > > > >_______________________________________________ > >MeeGo-dev mailing list > >[email protected] > >http://lists.meego.com/listinfo/meego-dev > > _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
