On Mon, Sep 22, 2008 at 7:37 AM, Rohit <[EMAIL PROTECTED]> wrote:
>
> When I send a put request for updating an existing calendar entry, I
> get back 400 bad request response. I found that at first 302 redirect
> is received and in subsequent POST 400 is received back.
> I made the following change and it started working good.
>
> File- src/gdata/service.py
> Method- PostOrPut
> Line-940
> return self.Post(data, location, extra_headers, url_params,
> escape_params, redirects_remaining - 1, media_source,
> converter=converter)
>
> Changed this statement to
>
> return self.PostOrPut(verb, data, location, extra_headers, url_params,
> escape_params, redirects_remaining - 1, media_source,
> converter=converter)
>
> Before this change both PUT and POST redirects were followed by POST
> request. While it looks reasonable to send a PUT in response to PUT
> redirect and POST in response POST redirect which exactly this
> modifications does, I am not sure if this really is an issue with API
> or something else.
Hi Rohit,
That certainly seems like a reasonable change to make. Jeff Scudder
opened up a defect report for this in the gdata-python-client tracker
here:
http://code.google.com/p/gdata-python-client/issues/detail?id=168
Feel free to star it if you'd like to know when this change makes it
into a release.
--
Trevor Johns
--~--~---------~--~----~------------~-------~--~----~
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
google-calendar-help-dataapi@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
