Yes, the OAuth credentials have to be passed in the "Authorization" header.
On Fri, Nov 18, 2011 at 9:14 AM, James Lampert <[email protected]>wrote: > Alain Vongsouvanh wrote: > >> Exactly :) >> > > Dear Mr. Vongsouvanh: > > Sorry to keep bugging you. > > I just learned of an exit-hook in HTTPAPI, for "additional header(s)" (up > until this morning, I wasn't aware that HTTPAPI even HAD exit hooks). Are > the 2-legged OAuth credentials to be passed as an additional header, e.g., > > > Header = 'Authorization: OAuth ' > > + 'oauth_version="1.0", ' > > + 'oauth_nonce="**1c4fbbe4387a685829d5938a3d9798**8c", ' > > + 'oauth_timestamp="1227303732", ' > > + 'oauth_consumer_key="example.**com <http://example.com>", ' > > + 'oauth_signature_method="HMAC-**SHA1", ' > > + 'oauth_signature="lqz%2F%**2BfwtusOas8szdYd0lAxC8%3D" '; > > (from a fellow HTTPAPI List member, based on the 2-legged-OAuth POST to > Google Docs example) > > or something similar? > > > -- > JHHL > > -- > 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 > google-calendar-help-dataapi@**googlegroups.com<[email protected]> > To unsubscribe from this group, send email to > google-calendar-help-dataapi+**[email protected]<google-calendar-help-dataapi%[email protected]> > For more options, visit this group at > http://code.google.com/apis/**calendar/community/forum.html<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
