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' by the OpenDNS server (google.navigation.opendns.com/208.67.219.230). However, connecting directly to a known IP (retrieved by looking up www.google.com from a 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 <[EMAIL PROTECTED]> 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" <[EMAIL PROTECTED]> > wrote: > > > Any updates ? > > > On 4/26/07, Ryan Boyd (Google) <[EMAIL PROTECTED]> 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)" <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
