Tatiana,
It seems like Google has different calendars on different servers, and one purpose of the redirects is to set the gsessionid cookie/url parameter so that each request goes to the correct server for that calendar. Another purpose could be to share the load over various servers. It is possible that Google has moved some subset of your domain's calendars to a different server, but that this movement has exposed either some error in Google's configuration or infrastructure, or an error in your code. Some questions for you to zone into what is going wrong: Are some or all of your PUTs being redirected? Are you following the redirects? What URL are you following them to? Could there be some error in your handling of redirects or an error in the server that is handling the redirects? Are the errors uniform in terms of the calendars that have errors and those that don't. If you repeat the exact same PUTs to the same URLs 20 minutes later, do the same 1 out of twenty fail? I see that some succeed after failing, but is it always the same ones that fail? Ray On Sep 9, 2008, at 10:42 AM, Tatiana wrote: > > We are trying to update the summary for calendars in our domain > student.leedsmet.ac.uk, This worked absolutely successfully in 100% of > cases on Friday 5.09.2008. > > Trying to update summaries today - one in twenty calendars returns > "Invalid request URI.(400 Bad request)" error. > > An example: > > We are sending PUT request to following URL : > > http://www.google.com/calendar/feeds/default/owncalendars/full/student.leedsmet.ac.uk_kmm5nj000j9dfq3dtrubdad194%40group.calendar.google.com > > With the following body of the request: > > <entry xmlns='http://www.w3.org/2005/Atom' xmlns:gd='http:// > schemas.google.com/g/2005' xmlns:gCal='http://schemas.google.com/gCal/ > 2005'> > <id>http://www.google.com/calendar/feeds/default/owncalendars/full/ > kmm5nj000j9dfq3dtrubdad194%40group.calendar.google.com</id> > <title type='text'>TEST_TIMETABLE_77011500</title> > <summary type='text'>Welcome to this Google calendar version of your > timetable. It is updated every night from the main online timetable > system, so if any changes are made to your main timetable during the > day for that same day, it may not be 100% accurate. Please note that > this timetable does not indicate whether an event is a drop-in session > or timetabled class. Please compare this Google calendar timetable to > your printed timetable. If the two timetables are the same please send > an email confirming this to [EMAIL PROTECTED] If you find > any differences please liaise with your faculty contact, who will > forward your reply to us. All replies received by the end of 3rd > October will be entered into a draw with a Leeds Met Google hoodie as > the prize!</summary> > <gd:where rel='' label='' valueString='Leeds Metropolitan > University'></gd:where> > </entry> > > This returns "Invalid request URI.(400 Bad request) error". > > My questions are below, will be thankful to anyone for any answers: > > 1) Why 19 out of 20 calendars, processed in a loop, in the absolutely > same way, have the summary updated successfully and 1 out of 20 > doesn't? > > 2) Why is the error not consistent? When trying to perform the update > of the summary for the calendars where it failed: When I try to update > again and again sometimes (rarely) I receive "200 OK ". > > 3) What does "Invalid request URI" mean????????? > > > -- Ray Baxter http://67central.com/bc/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
