Ya I had a look at the request headers and if you have a google cookie it is passing a timezone in that. it was a numbered time so my server in Houston sent a cookie with a timezone of 480.
I now use only very explicit parameters in my requests. The site I am working on is a community portal so all timezones should be Pacific but my server that is requesting the feed via the API is in Texas and is the system time is set to UTC. So I set the calendar settings to Pacific, then I pass the ctv=America/ Pacific, and a startmin and a startmax, then sortby startdate and sort ascending. And then I double check the dates on their way out to the response object just to be sure :) Seems to be working again now. D On Dec 16, 6:39 pm, Simon G <[email protected]> wrote: > lonecrow - your right it isn't client specific but location of client > specific. Mylinuxsystem is in Texas, others have problems when the > system is in Colorado,curlonlinuxhere in Nova Scotia, or in UK or > Denmark works fine. The same API call produces different results in > different locations. Are google rolling out some modifcation that has > broken selecting by date completely -- I have posted separately about > this. > > On Dec 16, 7:23 pm, lonecrow <[email protected]> wrote: > > > It shouldn't have anything to do with the requesting client. If the > > feed is passed the parameter for future events only, that is all it > > should return. It is clearly a server side issue. > > > caffeinePete's post makes sense, in that without a time zone from the > > client how can the server know what the future is? > > > I can't say that it was "the" fix, but I had the same intermittent > > problem. It wasn't until I added a time to my start-min and added a > > ctz that I stopped seeing that behavior. > > > On Dec 16, 9:30 am, Simon G <[email protected]> wrote: > > > > I have this problem, I think it is one and the same the future event > > > problem reported as well. > > > > A feed for future event from my calendar is > > > > http://www.google.com/calendar/feeds/[email protected]/public/full?futureevents=true&sortorder=ascendin > > > > > > g&orderby=starttime&singleevents=true&hl=en&ctz=Europe/London&max-results=5 > > > >CurlonLinux-incorrectresult, oldest events > > > Lynx onLinux-incorrectresult, oldest events > > > IE8 Vista -incorrectresult, oldest events > > > FF3.5 Vista - correct > > > Chrome Vista - correct > > > > The issue fromCurlwill effect many php libraries as they often use > > >Curlto go grab the data. > > > > On Dec 15, 8:31 am, caffeinePete <[email protected]> wrote: > > > > > I can't say that it was "the" fix, but I had the same intermittent > > > > problem. It wasn't until I added a time to my start-min and added a > > > > ctz that I stopped seeing that behavior. > > > > > Cheers > > > > > On Dec 14, 4:53 pm, Josh Shea <[email protected]> wrote: > > > > > > It appears that the Google Calendar API is sometimes returning the > > > > > full calendar (that is, all events since we started using it in 2008) > > > > > even when we specify a specific date range. The problem appears > > > > > intermittent, in that it does return the correct, expected events some > > > > > of the time, and some of the time (about 1 out of every 5 requests) it > > > > > returns the entire calendar since we started using it. > > > > > > We are using the Zend library to make the requests to the API. the > > > > > following is the request array that, like I said, works most of the > > > > > time: > > > > > >Zend_Gdata_Calendar_EventQueryObject > > > > > ( > > > > > [_defaultFeedUri:protected] =>http://www.google.com/calendar/feeds > > > > > [_comments:protected] => > > > > > [_user:protected] => ********* > > > > > [_visibility:protected] => public > > > > > [_projection:protected] => full-noattendees > > > > > [_event:protected] => > > > > > [_params:protected] => Array > > > > > ( > > > > > [orderby] => starttime > > > > > [sortorder] => a > > > > > [start-min] => 2009-12-01 > > > > > [start-max] => 2010-01-01T00:00:00 > > > > > [singleevents] => true > > > > > ) > > > > > > [_url:protected] => > > > > > [_category:protected] => > > > > > ) > > > > > > I'm just wondering if anyone else has encountered this problem, or has > > > > > found a reason why this is happening - either an error in our code or > > > > > in the API itself. > > > > > > Thanks for your assistance. > > > > > > ~js -- 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.
