Mind your spaces and linefeeds. The HTTP protocol is very specific about the location and number. 0d0a0d0a won't work where the spec says 0a0a, but they look the same in Notepad.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] 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 Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
