RE: Troubleshooting a call to Google Calendar web services from HTTPAPI (cross-posted to MIDRANGE-L and the HTTPAPI List)

[Mike Krebs <mkrebs@xxxxxxxxxxxxxxxxxx>]

The nonce has not been used before?

Could you post enough of the playground and your debug that we can look it over ourselves? Obviously put some Xs in to obfuscate the secrets.

Or post code and we can try to authenticate to our own apps.



-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Monday, November 28, 2011 6:37 PM
To: Midrange Systems Technical Discussion; HTTPAPI and FTPAPI Projects
Subject: Troubleshooting a call to Google Calendar web services from HTTPAPI (cross-posted to MIDRANGE-L and the HTTPAPI List)

I've gotten as far as sending a request through HTTPAPI to the Google 
Calendar web services, but I'm getting back
     HTTP/1.1 401 Unknown authorization header."

The request, and the authorization header, except for the timestamp and 
nonce, and the resulting signature, appear to be identical to what I 
successfully sent from the "OAuth Playground" last week. I've worked 
through all of the obvious typos, and can't make head or tail of what 
else could be causing it to fail.

Anybody got any insights?

--
JHHL
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------