Hi Mark, Thanks for your reply! Screen name of the account is dmlreach. Please see the request and 2 responses.
Request: GET /1/account/verify_credentials.xml HTTP/1.1 Authorization: Basic <MY_AUTH_STRING_HERE> Host: api.twitter.com OK response headers: Status: 200 OK X-Transaction: 1269267625-43203-17004 X-RateLimit-Limit: 20000 X-RateLimit-Remaining: 19998 X-Runtime: 0.06217 Pragma: no-cache X-RateLimit-Class: api_whitelisted X-Revision: DEV X-RateLimit-Reset: 1269271222 Content-Length: 2730 Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Content-Type: application/xml; charset=utf-8 Date: Mon, 22 Mar 2010 14:20:25 GMT Expires: Tue, 31 Mar 1981 05:00:00 GMT ETag: "1f0dfa0c9c82fe48bec465b9bad3793a" Last-Modified: Mon, 22 Mar 2010 14:20:25 GMT Set-Cookie: guest_id=1269267625681; path=/,lang=en; path=/,_twitter_sess=BAh7CToRdHJhbnNfcHJvbXB0MDoPY3JlYXRlZF9hdGwrCOn2PoYnAToHaWQi %250AJWIyNDJhNjNkZjI1MzVkZDBmMWE5ODExZWMxOGE1ZjRkIgpmbGFzaElDOidB %250AY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA-- bbde5312124b201f3cead86cb3d7e2947579ab88; domain=.twitter.com; path=/ Server: hi Vary: Accept-Encoding Connection: close 401 response headers: Status: 401 Unauthorized X-Runtime: 0.00763 Content-Length: 155 Cache-Control: no-cache, max-age=1800 Content-Type: application/xml; charset=utf-8 Date: Mon, 22 Mar 2010 14:04:48 GMT Set-Cookie: guest_id=1269266688016; path=/,_twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCBeoMIYnAToHaWQiJWE1ZjZhMDdjZDA5OWUy %250AZjM1ZDFmMmY5Mzc1YWFjMTQ4IgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy %250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA-- fcdae0e1bde0a38c30903e86171f6b7a26afa0d0; domain=.twitter.com; path=/ Server: hi WWW-Authenticate: Basic realm="Twitter API" Expires: Mon, 22 Mar 2010 14:34:47 GMT Vary: Accept-Encoding Connection: close So, in response to the same request I got two different responses. Both requests were made from the same server. I would be very grateful if someone could help me with this issue. On Mar 17, 7:29 pm, Mark McBride <mmcbr...@twitter.com> wrote: > Without more details it's tough to say. Do you at least have the screen > name of the account in question, and details on both the success and failure > environments? > > ---Mark > > http://twitter.com/mccv > > On Wed, Mar 17, 2010 at 1:39 AM, Uladzimir Pashkevich < > > v.pashkev...@gmail.com> wrote: > > Does anyone has any ideas? Any help is really appreciated, because I > > can't understand this kind of the API's behavior. > > > On Mar 12, 6:40 pm, Uladzimir Pashkevich <v.pashkev...@gmail.com> > > wrote: > > > Hi everyone, > > > > I am developing an application using Twitter API and I have > > > encountered into a strange behavior connected with 401 error. I am > > > using basic auth. When I run my application locally, it works just > > > fine and I never get any 401 errors. However, when I run my > > > application on another environment, I get 401 error in approximately > > > 80% cases. I am completely sure that the credentials are correct. > > > > What makes this situation even more weird is that I am working with > > > several accounts, and most of them work fine in both environments. I > > > am experiencing problems only with one account. All accounts I work > > > with are whitelisted, so rate limit should not be an issue here. > > > > I have no idea what may cause this behavior. Could you please explain > > > me the possible reasons I am getting 401? > > > > Thanks, > > > Uladzimir To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
