Hi Alain - sorry, even the most up to date client library exhibits
this problem.

The HTTP headers look OK going in and out - can you suggest what to
look for??

Cheers

Jan

On Jun 11, 7:07 am, Alain Vongsouvanh <[email protected]> wrote:
> Hello Jan,
>
> This issue is a known issue with the Python client library. Please sync your
> client library with the repository in order to get the latest fixes:
>  http://code.google.com/p/gdata-python-client/source/checkout
>
> Best,
> Alain
>
> On Thu, Jun 9, 2011 at 11:27 PM, Jan Zawadzki / Hapara <
>
>
>
>
>
>
>
>
>
> [email protected]> wrote:
> > Alain, we're seeing a whole set of redirects, which is a bigger
> > problem - especially in environments like the App Engine, where too
> > many redirects either kills the urlfetch or forces us to hand-code the
> > redirect logic.
>
> > For us, the 302 is associated with reaching max-redirects (5 I
> > believe) - is this really to be expected?
>
> > Jan
>
> > On Jun 10, 4:13 am, Alain Vongsouvanh <[email protected]> wrote:
> > > Hello,
>
> > > The redirect is an expected behavior as it is needed by the API to make
> > sure
> > > that your requests land where your data is located.
>
> > > The client library should take care of handling the redirect, but
> > overriding
> > > the methods might lead to those issues.
>
> > > Best,
> > > Alain
>
> > > On Wed, Jun 8, 2011 at 10:38 AM, Kulvinder <[email protected]>
> > wrote:
> > > > I just figured out the issue myself. I recently had changed a method in
> > my
> > > > google overridden library as :
>
> > > >  public new TEntry Insert<TEntry>(Uri feedUri, TEntry newEntry) where
> > > > TEntry : EventEntry
> > > >         {
> > > >             SetWebProxy(feedUri);
> > > >             return base.Insert(feedUri, newEntry);
> > > >         }
>
> > > > when i change it back to :
>
> > > > public new EventEntry Insert(Uri feedUri, AtomEntry newEntry)
> > > >         {
> > > >             SetWebProxy(feedUri);
> > > >             return base.Insert(feedUri, newEntry) as EventEntry;
> > > >         }
>
> > > > It worked fine. Can somebody at google check the issue in API code ?
>
> > > > Frank, can you help ? Do you remember me ?
>
> > > > Thanks
>
> > > > --
> > > > 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://code.google.com/apis/calendar/community/forum.html
>
> > > --
> > > Alain Vongsouvanh
>
> > --
> > 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://code.google.com/apis/calendar/community/forum.html
>
> --
> Alain Vongsouvanh

-- 
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://code.google.com/apis/calendar/community/forum.html

Reply via email to