I am writing code for NodeJS, so there is no client library that I can use.

I want to follow the redirect rather than the cookie because I want to keep 
things simple for now and use a stateless protocol.

The issue is that I want to load a feed with query parameters, such as:

https://www.google.com/calendar/feeds/default/private/full?q=wedding&max-results=1&alt=jsonc

Though in making that request, I do not access that URL, but one with a 
bunch of oauth query parameters:

https://www.google.com/calendar/feeds/default/private/full?q=wedding&max-results=1&alt=jsonc&oauth_consumer_key=XXX&oauth_nonce=7zxt5E&oauth_signature_method=HMAC-SHA1&oauth_timestamp=1316802619&oauth_token=XXX&oauth_version=1.0

Also included in that request is the "oauth_signature" header.

The response I get from Google drops all of my query parameters and simply 
has a gsessionid query parameter:

https://www.google.com/calendar/feeds/default/private/full?gsessionid=ZZZ

So the question is, in performing the redirect, which sets of query 
parameters do I need:

* gsessionid
* q, max-results, alt
* oauth_*

And is it the original value for the oauth_signature header? Or should I be 
creating a new oauth_nonce and oauth_timestamp and recalculating everything?

I have tried a number of permutations, but no matter what I do, I seem to 
get a response that disregards my query parameters.

-- 
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