[twitter-dev] Re: 401 Unauthorized Responses to requests signed with whitelisted account
Hi Matt,
Thank you so much for your timely response. Your suggestion was very
helpful - I logged the response body and am seeing the following
error:
Invalid / suspended application
I really don't know why that would be - does that mean that we are
blacklisted? I should point out a few things that you will probably
want to know:
1. We have a conservative and fairly sophisticated throttling system
to prevent us from over-stepping the rate limit (I don't think that's
the problem...)
2. On Saturday I received a message from the API support team
confirming that our whitelisted account was in good standing (can
provide the message if it's helpful)
3. We've seen the rate limit reported in the response change back and
forth somewhat sporadically...
Thank you again for any help you can provide - in general we are very
pleased with the API and we certainly appreciate your support!
Best,
Chris
On Apr 18, 3:44 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Christopher,
Could you attempt to get the response body for the request either by
repeating the request or enhancing your logs. The reason for the 401 is
communicated in the response body and knowing that will help explain what is
going on.
Best,
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Mon, Apr 18, 2011 at 11:23 AM, Christopher Stolte
stolte...@gmail.comwrote:
Hello,
I am a Java developer working on a web application that makes use of
the Twitter API. We use the Signpost library (version 1.2.1.1) to
perform OAuth and issue API requests, and have been doing so
successfully for months. We have been signing our requests with a
whitelisted key and secret that has a 20,000 request/hour rate limit.
In the last few days, we started getting only 401 Not Authorized
responses when using these credentials. Upon looking back at our
server logs, I notice other requests failures dating back to at least
Feb 17, but they are sporadic. Error messages look like this:
WARN org.apache.http.impl.client.DefaultHttpClient Authentication
error: Unable to respond to any of these challenges: {oauth=WWW-
Authenticate: OAuth realm=http://api.twitter.com}
The response header shows 401 but no other enlightening information.
I have paid attention to and read lots of other postings related to
OAuth, and want to emphasize that our system has been working for
quite a while - we make calls using the proper end points and so
forth:
http://api.twitter.com/1/users/show.json?user_id=[id]
Something appears to have changed on Twitter's end but we don't know
what.
Can anyone shed some light on what might be happening? We have
already verified with Twitter API support that our credentials should
still be viable - perhaps there has been an inadvertent shutdown of
that account?
Thank you in advance for any help or guidance!
Sincerely,
Chris Stolte
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
[twitter-dev] Re: 401 Unauthorized Responses to requests signed with whitelisted account
Hi Matt,
Thank you so much for your timely response. Your suggestion was very
helpful - I logged the response body and am seeing the following
error:
Invalid / suspended application
I really don't know why that would be - does that mean that we are
blacklisted? I should point out a few things that you will probably
want to know:
1. We have a conservative and fairly sophisticated throttling system
to prevent us from over-stepping the rate limit (I don't think that's
the problem...)
2. On Saturday I received a message from the API support team
confirming that our whitelisted account was in good standing (can
provide the message if it's helpful)
3. We've seen the rate limit reported in the response change back and
forth somewhat sporadically...
Thank you again for any help you can provide - in general we are very
pleased with the API and we certainly appreciate your support!
Best,
Chris
On Apr 18, 3:44 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Christopher,
Could you attempt to get the response body for the request either by
repeating the request or enhancing your logs. The reason for the 401 is
communicated in the response body and knowing that will help explain what is
going on.
Best,
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Mon, Apr 18, 2011 at 11:23 AM, Christopher Stolte
stolte...@gmail.comwrote:
Hello,
I am a Java developer working on a web application that makes use of
the Twitter API. We use the Signpost library (version 1.2.1.1) to
perform OAuth and issue API requests, and have been doing so
successfully for months. We have been signing our requests with a
whitelisted key and secret that has a 20,000 request/hour rate limit.
In the last few days, we started getting only 401 Not Authorized
responses when using these credentials. Upon looking back at our
server logs, I notice other requests failures dating back to at least
Feb 17, but they are sporadic. Error messages look like this:
WARN org.apache.http.impl.client.DefaultHttpClient Authentication
error: Unable to respond to any of these challenges: {oauth=WWW-
Authenticate: OAuth realm=http://api.twitter.com}
The response header shows 401 but no other enlightening information.
I have paid attention to and read lots of other postings related to
OAuth, and want to emphasize that our system has been working for
quite a while - we make calls using the proper end points and so
forth:
http://api.twitter.com/1/users/show.json?user_id=[id]
Something appears to have changed on Twitter's end but we don't know
what.
Can anyone shed some light on what might be happening? We have
already verified with Twitter API support that our credentials should
still be viable - perhaps there has been an inadvertent shutdown of
that account?
Thank you in advance for any help or guidance!
Sincerely,
Chris Stolte
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
Re: [twitter-dev] Re: 401 Unauthorized Responses to requests signed with whitelisted account
Hi Chris,
Our policy team are the beat ones to contact about this as they have access to
the information about why the app was suspended. You can contact them through
a...@twitter.com .
When you contact them let then know what you've put in the email below and
include the ticket number of your previous communication with them.
They will be able to let you know the next steps.
Best
@themattharris
On Apr 19, 2011, at 8:57, Christopher Stolte stolte...@gmail.com wrote:
Hi Matt,
Thank you so much for your timely response. Your suggestion was very
helpful - I logged the response body and am seeing the following
error:
Invalid / suspended application
I really don't know why that would be - does that mean that we are
blacklisted? I should point out a few things that you will probably
want to know:
1. We have a conservative and fairly sophisticated throttling system
to prevent us from over-stepping the rate limit (I don't think that's
the problem...)
2. On Saturday I received a message from the API support team
confirming that our whitelisted account was in good standing (can
provide the message if it's helpful)
3. We've seen the rate limit reported in the response change back and
forth somewhat sporadically...
Thank you again for any help you can provide - in general we are very
pleased with the API and we certainly appreciate your support!
Best,
Chris
On Apr 18, 3:44 pm, Matt Harris thematthar...@twitter.com wrote:
Hi Christopher,
Could you attempt to get the response body for the request either by
repeating the request or enhancing your logs. The reason for the 401 is
communicated in the response body and knowing that will help explain what is
going on.
Best,
@themattharris
Developer Advocate, Twitterhttp://twitter.com/themattharris
On Mon, Apr 18, 2011 at 11:23 AM, Christopher Stolte
stolte...@gmail.comwrote:
Hello,
I am a Java developer working on a web application that makes use of
the Twitter API. We use the Signpost library (version 1.2.1.1) to
perform OAuth and issue API requests, and have been doing so
successfully for months. We have been signing our requests with a
whitelisted key and secret that has a 20,000 request/hour rate limit.
In the last few days, we started getting only 401 Not Authorized
responses when using these credentials. Upon looking back at our
server logs, I notice other requests failures dating back to at least
Feb 17, but they are sporadic. Error messages look like this:
WARN org.apache.http.impl.client.DefaultHttpClient Authentication
error: Unable to respond to any of these challenges: {oauth=WWW-
Authenticate: OAuth realm=http://api.twitter.com}
The response header shows 401 but no other enlightening information.
I have paid attention to and read lots of other postings related to
OAuth, and want to emphasize that our system has been working for
quite a while - we make calls using the proper end points and so
forth:
http://api.twitter.com/1/users/show.json?user_id=[id]
Something appears to have changed on Twitter's end but we don't know
what.
Can anyone shed some light on what might be happening? We have
already verified with Twitter API support that our credentials should
still be viable - perhaps there has been an inadvertent shutdown of
that account?
Thank you in advance for any help or guidance!
Sincerely,
Chris Stolte
--
Twitter developer documentation and resources:http://dev.twitter.com/doc
API updates via Twitter:http://twitter.com/twitterapi
Issues/Enhancements Tracker:
http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
--
Twitter developer documentation and resources: http://dev.twitter.com/doc
API updates via Twitter: http://twitter.com/twitterapi
Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list
Change your membership to this group:
http://groups.google.com/group/twitter-development-talk
