When my application had OAuth I was doing all of the requests using
OAuth in the headers and it worked fine... Perhaps you are experiencing
a transient issues. If you have never been able to make a protected
resource request there may be an error in your implementation.
Dimebrain wrote:
Just out of curiousity are you supporting the Authorization header
form of OAuth when making protected resource requests? I know they
work for tokens, but wondered if a call to verify_credentials for
instance needed to use parameters or if it could continue to use the
Authorization header?
On Mar 27, 2:20 am, Dimebrain <daniel.cre...@gmail.com> wrote:
I am able to consistently exchange the request token for the access
token and see my application in the Connections tab for my account.
However, I'm no longer able to make protected resource requests with
the final token and secret. It worked for me earlier in the evening,
but now is consistently returning "Invalid / expired Token" for any
authenticated call I make.
