Thanks to you Ryan, Jole and Basia and the OpenDNS Guys. All helped very 
quickly and promptly.
   
  Thanks again.

"Ryan Boyd (Google)" <[EMAIL PROTECTED]> wrote:
  
Thanks to Kulvinder, Basia, and Mark for all the detailed debugging
information. Thanks especially to jole for finding the common factor
leading to these issues.

Happy coding!

-Ryan


On Apr 30, 8:25 am, "Ryan Boyd (Google)" wrote:
> Thanks very much david for pulling out the 'occassional network
> operator' hat and resolving this problem so quickily!
>
> Cheers,
> -Ryan
>
> On Apr 30, 8:12 am, davidu wrote:
>
> > On Apr 30, 5:48 am, jole wrote:
>
> > > Thank you 100x, I appreciate your rapid response.
>
> > Thanks. I'm sorry I didn't see this thread earlier.
>
> > Thanks to Ryan Boyd @ Google for helping to give me a complete picture
> > of what was happening and thanks to you, Jole, for getting the ball
> > rolling on debugging this.
>
> > -david
>
> > > On Apr 30, 4:18 am, Basia wrote:
>
> > > > Yes I am using OpenDNS and have tried running the code today and it
> > > > seems to work. Thank you Ryan and davidu for helping out with this
> > > > problem....I really appreciate it.
>
> > > > Basia
>
> > > > On Apr 30, 2:12 am, davidu wrote:
>
> > > > > I went ahead and pushed out a fix for this. Can someone who uses the
> > > > > API confirm that it's working?
>
> > > > > I'll have a more detailed explanation in the morning for those who'd
> > > > > like it.
>
> > > > > Thanks,
> > > > > David Ulevitch
> > > > > OpenDNS (CEO and occasional network operator) :-)
>
> > > > > On Apr 29, 6:44 pm, "Ryan Boyd (Google)" wrote:
>
> > > > > > Thanks very much jole for that information - it is very helpful!
>
> > > > > > I tried out the OpenDNS system-- and yes, their proxy servers appear
> > > > > > to be stripping the Authorization headers being sent to the Calendar
> > > > > > data API. I tried running a curl script to retrieve a calendar feed
> > > > > > using an authorization header correctly retrieved from clientlogin--
> > > > > > This does not work correctly (returns a 401) when using the host
> > > > > > returned for 'www.google.com'bytheOpenDNSserver
> > > > > > (google.navigation.opendns.com/208.67.219.230). However, connecting
> > > > > > directly to a known IP (retrieved by looking upwww.google.comfroma
> > > > > > non-OpenDNS DNS server)-- the same request worked fine. I have
> > > > > > contacted OpenDNS to see if they can look into the issue.
>
> > > > > > Kulvinder, Basia and Mark -- can any of your reports possibly be
> > > > > > related to using the OpenDNS DNS / proxy servers?
>
> > > > > > Thanks,
>
> > > > > > -Ryan
>
> > > > > > On Apr 29, 2:03 pm, jole wrote:
>
> > > > > > > Try disabling OpenDNS, it seems that they are 
> > > > > > > cachinghttp://google.com/accounts
> > > > > > > incorrectly, causing 401's all over the place.
>
> > > > > > > On Apr 27, 12:41 am, "Kulvinder Singh" 
> > > > > > > wrote:
>
> > > > > > > > Any updates ?
>
> > > > > > > > On 4/26/07, Ryan Boyd (Google) wrote:
>
> > > > > > > > > Hi Mark,
>
> > > > > > > > > And, actually, if you could check with your colleague and see 
> > > > > > > > > if you
> > > > > > > > > can send me the account name that was able to authenticate 
> > > > > > > > > correctly,
> > > > > > > > > I'd appreciate that as well.
>
> > > > > > > > > Thanks,
> > > > > > > > > -Ryan
>
> > > > > > > > > On Apr 26, 8:48 am, "Ryan Boyd (Google)" wrote:
> > > > > > > > > > Mark,
>
> > > > > > > > > > Thanks for the additional information Mark.
>
> > > > > > > > > > Can you please send me the username (privately if you wish) 
> > > > > > > > > > that you
> > > > > > > > > > are using when you're not able to authenticate?
>
> > > > > > > > > > Thanks,
>
> > > > > > > > > > -Ryan
>
> > > > > > > > > > On Apr 26, 8:42 am, Mark Milliman wrote:
>
> > > > > > > > > > > Thank goodness someone else is seeing this problem. I 
> > > > > > > > > > > have been
> > > > > > > > > > > experiencing it for a few days now. I have been receiving
> > > > > > > > > > > authorization failures on an Outlook add-in using .NET 
> > > > > > > > > > > and my GDT
> > > > > > > > > > > calendar gadget. Both are sending me replies that 
> > > > > > > > > > > authentication
> > > > > > > > > > > failed. I knew my user ID and password were correct. I 
> > > > > > > > > > > changed my
> > > > > > > > > > > password, but that did not help. I even logged into 
> > > > > > > > > > > another account
> > > > > > > > > > > and received the same problem. A colleague tried the same 
> > > > > > > > > > > tests in
> > > > > > > > > > > another state and everything worked fine. The only 
> > > > > > > > > > > differences that I
> > > > > > > > > > > could detect was that his UID was his gmail ID and mine 
> > > > > > > > > > > was my e-mail
> > > > > > > > > > > address and he is located in a different state possibly 
> > > > > > > > > > > served by
> > > > > > > > > > > different servers with a different version of the API.
>
> > > > > > > > > > > I tried to authenticate myself and get a token just to 
> > > > > > > > > > > retrieve my
> > > > > > > > > > > calendars and add an appointment. Both failed. The only 
> > > > > > > > > > > way I can
> > > > > > > > > > > view my calendar is to open Firefox and view it. GDT and 
> > > > > > > > > > > Outlook are
> > > > > > > > > > > useless because of this issue. Until last night, I 
> > > > > > > > > > > thought that the
> > > > > > > > > > > problem was on my end. Now I am certain that it is an API 
> > > > > > > > > > > issue.
> > > > > > > > > > > What has changed from Google's perspective? When can we 
> > > > > > > > > > > see a
> > > > > > > > > > > resolution?
>
> > > > > > > > > > > Thanks,
> > > > > > > > > > > Mark





       
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
 Check outnew cars at Yahoo! Autos.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to