On 5/29/13 3:28 PM, Jeff Johnson wrote:
> On 05/29/2013 02:41 PM, Paul McNett wrote:
>> On 5/29/13 2:27 PM, Jeff Johnson wrote:
>>> I have googled it and tried many variations of the request.  What I am 
>>> getting is a
>>> 302 redirect.  I have tried using the id where the entry was redirected and 
>>> all sorts
>>> of suggestions, but I am stumped.
>> Have you read:
>>
>> https://developers.google.com/google-apps/calendar/v2/developers_guide_protocol
>>
>> and searched for 302 in that page?
>>
>> Paul
> Paul:  Yes.  I have been using that as well as the Python documentation.  
> Also in
> Googling the redirects there is some argument as to whether or not it is a 
> bug.  The
> Python coders say that it is intermittent and therefore does not need fixing.
> Basically what happens is that the original entry is temporarily moved and 
> give a
> gsessionid.  I pick that up and call it again but it still redirects.  It 
> appears
> that a whole bunch of developers are experiencing it and I have not found a 
> solution
> as of yet.  I have tried several work a rounds which did not work either.  I 
> was just
> wondering if anyone in here has any experience with accessing calendar events 
> from
> two different sources.  ie, an application and a smart phone.  If I access 
> everything
> from the application it works 100% including updates.

Well if a whole bunch of devs are seeing a problem, that's probably good news.

Paul



_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: 
http://leafe.com/archives/byMID/profox/[email protected]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to