× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. November 2011

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

James

I don't know what you need different - but you might install Wireshark, to see what is leaving your computer from OAuth - and a comm trace on i to see what goes out there.

Wireshark is free - fantastic big hammer for network issues

HTH
Vern

On 11/28/2011 6:37 PM, James Lampert wrote:
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

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.