There's not quite enough output in your email to help you debug this issue. Also, we'd need to know which library you're using for OAuth.
On Sun, Apr 5, 2009 at 22:58, agiorlando <[email protected]> wrote: > > I uploaded the OAuth live example source code to my server and plugged > in my keys. It doesn't work for some reason, the headers it spits back > at me after allowing read access are: > > HTTP/1.1 401 Unauthorized > Date: Mon, 06 Apr 2009 05:56:10 GMT > Server: hi > Status: 401 Unauthorized > WWW-Authenticate: Basic realm="Twitter API" > Cache-Control: no-cache, max-age=1800 > Content-Type: application/xml; charset=utf-8 > Content-Length: 152 > Set-Cookie: > _twitter_sess=BAh7BzoHaWQiJTE4ODg3YTZkOTM5MGQ5NzIzODQ0MGM5NmVjMDU0ZWE4Igpm > %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG > %250AOgpAdXNlZHsA--7d2be6af75c7d76c08c88ae22f6473709d8a98e2; > domain=.twitter.com; path=/ > Expires: Mon, 06 Apr 2009 06:26:10 GMT > Vary: Accept-Encoding > Connection: close > > It says "hi", and that is the weirdest thing to me. :S > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
