Hi,
When you get an HTTP 401 there should be a body, Something like:
"Failed to validate oauth signature or token", or the more informative
"Invalid / expired token", or a host of other things. The "401
Unauthorized" is the HTTP status line itself and is the error we use
for all OAuth failures. If you're using a library to access Twitter
via OAuth perhaps it is not displaying the body message be default. If
that's the case I recommend adding some print statements, using a
debugging proxy (such as Charles), or watching via tcpdump (or
equivalent) so you can see the body.
Also helpful for debugging just about any error with the API is
the full request and response headers. Look at this from my
perspective … right now I have even less to go on than you. I don't
know your code, what request you made, and I cannot debug interactively.
Thanks;
— Matt Sanford
ProTip: When reporting bugs try to remember that no matter how
frustrated you are you're asking someone who is not sitting with you
and is not in the same frame of mind. This is like shouting at the
police when you called them. Therapeutic? yes. Helpful? probably not.
Good matrial for the show Cops? definitely.
On Jun 25, 2009, at 9:45 AM, Obrzut wrote:
The remote server returned an error: (401) Unauthorized.
This is the exact error. I was not being hostile - just going out my
wits end! *smiles*
I've de-stressed by laying in bed for the past hour trying to forget
about the Twitter API and OAuth. Ha!
That said - shall I include the URL I am using with Parameters?
Perhaps that will help, no? I'll get right on that.
