Thanks, turns out I was misinterpreting my responses. I was assuming
that a location header was a 302 (I know, I know, but I was using
someone elses code on another project to get me started). Anyways, I
re-factored it and I realized that my first two redirects were actually
a 302, followed by a 201, followed by the 400, which makes perfect
sense.
Thanks.
On Nov 22, 3:28 pm, "Ryan Boyd (Google)" <api....@google.com> wrote:
Hi,
When an event is added, you should get a 201 response returned. An
event should not be added if you receive a 302 redirect and likely not
added as a result of a 400 response. In general, you should only see
one redirect per request. As long as you store the cookie returned
from the redirect and use that with your future requests, additional
redirects are currently rare.
Are you using a client library for posting to your calendar, or are you
crafting the HTTP requests yourself? Do you know what the body of the
400 response was (that should give an indication as to the error)?
Happy coding,
6 messages in com.googlegroups.google-calendar-help-dataapiRe: Code 400, entry still added