Hello Michael, Sorry about the delay in getting back to you! I'm glad you figured out how to handle Calendar API redirects. As you mentioned, you need to pass in all the original URL parameters in addition to the added gsessionid. Also, have you tried passing the Authorization parameters in the request header instead of passing them as URL parameters?
Best, Alain On Fri, Sep 23, 2011 at 9:21 PM, Michael Bolin <[email protected]> wrote: > Upon further experimentation, I believe the solution is to: > > (1) Take the original feed URL > (2) Add the gsessionid query parameter to the original feed URL, creating a > new URL. > (3) Create a fresh, signed request to the new URL. Because there is a new > query parameter, that will alter the "normalized string of parameters in the > request" used to construct the "base string" (language from > http://code.google.com/apis/accounts/docs/OAuth_ref.html#SigningOAuth). > > > -- > 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 > -- Alain Vongsouvanh | Developer Programs Engineer -- 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
