Re: [twitter-dev] Re: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine
Amit, Your endpoint is obsolete and no longer supported by Twitter. That's why you got the 403. Statuses/followers will succeed if you change it to http://api.twitter.com/1/statuses/followers.xml https://api.twitter.com/1/statuses/followers.xml BUT this API is deprecated. Read all about it here: http://dev.twitter.com/doc/get/statuses/followers Bill On 06/14/2011 12:38 AM, Amit Battan Ror wrote: Bill Working fine : https://twitter.com/statuses/friends_timeline.xml Not Working Giving 403 Error : https://twitter.com/statuses/followers.xml On Jun 14, 10:14 am, Amit Battan Rorbatta...@gmail.com wrote: Thanks Bill I will check and try to track URL .. On Jun 13, 9:07 pm, Bill Jacobsongabe...@gmail.com wrote: Amit, also seehttp://www.mailinglistarchive.com/html/twitter-development-talk@googl That's what helped me. -Bill On 06/13/2011 10:44 AM, Bill Jacobson wrote: I'm suggesting that you find out what endpoint (Twitter URL) your app is targeting, and make sure that it matches what is currently documented. If it doesn't match, correct it. That's what worked for me. On 06/13/2011 08:05 AM, Amit Battan Ror wrote: I am not getting the solution. and my API was working fine beofre 2 3 days.. but not now.. all other API except getFollowersIncludingCurrentStatus working ok and return proper output On Jun 13, 5:53 pm, Bill Jacobsongabe...@gmail.comwrote: Amit, I don't know your library, but in my case the 403 was accompanied by the message Not authorized to use this endpoint and the solution was to update to http://api.twitter.com/1[etc.];. Bill Jacobson On 06/13/2011 05:39 AM, Amit Battan Ror wrote: any idea guys On Jun 10, 4:33 pm, Amit Battan Rorbatta...@gmail.com wrote: Hi All I am using Twitter-OAuth-iPhonehttps://github.com/bengottlieb/Twitter-OAuth-iPhone I am calling [twitterObj getFollowersIncludingCurrentStatus:NO] for getting my friend list which was working fine. But from last two days its giving me the 403 error. -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed with error: Error Domain=HTTP Code=403 The operation couldn t be completed. (HTTP error 403.) As twitter api wiki 403 is due to crossing the limit of updates and DM but here in getFollowersIncludingCurrentStatus Why this error occurring and even list is not comes next day giving same 403 error. Thanks Amit Battan -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine
Amit, I don't know your library, but in my case the 403 was accompanied by the message Not authorized to use this endpoint and the solution was to update to http://api.twitter.com/1 [etc.]. Bill Jacobson On 06/13/2011 05:39 AM, Amit Battan Ror wrote: any idea guys On Jun 10, 4:33 pm, Amit Battan Rorbatta...@gmail.com wrote: Hi All I am using Twitter-OAuth-iPhonehttps://github.com/bengottlieb/Twitter-OAuth-iPhone I am calling [twitterObj getFollowersIncludingCurrentStatus:NO] for getting my friend list which was working fine. But from last two days its giving me the 403 error. -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed with error: Error Domain=HTTP Code=403 The operation couldn’t be completed. (HTTP error 403.) As twitter api wiki 403 is due to crossing the limit of updates and DM but here in getFollowersIncludingCurrentStatus Why this error occurring and even list is not comes next day giving same 403 error. Thanks Amit Battan -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine
I'm suggesting that you find out what endpoint (Twitter URL) your app is targeting, and make sure that it matches what is currently documented. If it doesn't match, correct it. That's what worked for me. On 06/13/2011 08:05 AM, Amit Battan Ror wrote: I am not getting the solution. and my API was working fine beofre 2 3 days.. but not now.. all other API except getFollowersIncludingCurrentStatus working ok and return proper output On Jun 13, 5:53 pm, Bill Jacobsongabe...@gmail.com wrote: Amit, I don't know your library, but in my case the 403 was accompanied by the message Not authorized to use this endpoint and the solution was to update to http://api.twitter.com/1[etc.];. Bill Jacobson On 06/13/2011 05:39 AM, Amit Battan Ror wrote: any idea guys On Jun 10, 4:33 pm, Amit Battan Rorbatta...@gmail.comwrote: Hi All I am using Twitter-OAuth-iPhonehttps://github.com/bengottlieb/Twitter-OAuth-iPhone I am calling [twitterObj getFollowersIncludingCurrentStatus:NO] for getting my friend list which was working fine. But from last two days its giving me the 403 error. -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed with error: Error Domain=HTTP Code=403 The operation couldn�t be completed. (HTTP error 403.) As twitter api wiki 403 is due to crossing the limit of updates and DM but here in getFollowersIncludingCurrentStatus Why this error occurring and even list is not comes next day giving same 403 error. Thanks Amit Battan -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] Re: Error 403 while getFollowers : Twitter Iphone MGTwitterEngine
Amit, also see http://www.mailinglistarchive.com/html/twitter-development-talk@googlegroups.com/2011-06/msg00256.html. That's what helped me. -Bill On 06/13/2011 10:44 AM, Bill Jacobson wrote: I'm suggesting that you find out what endpoint (Twitter URL) your app is targeting, and make sure that it matches what is currently documented. If it doesn't match, correct it. That's what worked for me. On 06/13/2011 08:05 AM, Amit Battan Ror wrote: I am not getting the solution. and my API was working fine beofre 2 3 days.. but not now.. all other API except getFollowersIncludingCurrentStatus working ok and return proper output On Jun 13, 5:53 pm, Bill Jacobsongabe...@gmail.com wrote: Amit, I don't know your library, but in my case the 403 was accompanied by the message Not authorized to use this endpoint and the solution was to update to http://api.twitter.com/1[etc.];. Bill Jacobson On 06/13/2011 05:39 AM, Amit Battan Ror wrote: any idea guys On Jun 10, 4:33 pm, Amit Battan Rorbatta...@gmail.comwrote: Hi All I am using Twitter-OAuth-iPhonehttps://github.com/bengottlieb/Twitter-OAuth-iPhone I am calling [twitterObj getFollowersIncludingCurrentStatus:NO] for getting my friend list which was working fine. But from last two days its giving me the 403 error. -- Twitter Request FD751461-39C4-4EAB-A0F7-D1ED262B19EA failed with error: Error Domain=HTTP Code=403 The operation couldn�t be completed. (HTTP error 403.) As twitter api wiki 403 is due to crossing the limit of updates and DM but here in getFollowersIncludingCurrentStatus Why this error occurring and even list is not comes next day giving same 403 error. Thanks Amit Battan -- Twitter developer documentation and resources: https://dev.twitter.com/doc API updates via Twitter: https://twitter.com/twitterapi Issues/Enhancements Tracker: https://code.google.com/p/twitter-api/issues/list Change your membership to this group: https://groups.google.com/forum/#!forum/twitter-development-talk
Re: [twitter-dev] statuses/home_timeline.xml returning text/html instead of text/xml
I'm expecting 'application/json' and am suddenly getting 'text/html'. On 07/19/2010 01:58 PM, Rich wrote: I'm seeing an increase in the home timeline returning a content-type of text/html instead of text/xml The actual body of the request is actually the correct XML response but my app checks for the correct HTTP header content-type. Is anyone else seeing this?
Re: [twitter-dev] statuses/home_timeline.xml returning text/html instead of text/xml
Request address was http://api.twitter.com/1/statuses/home_timeline.json?count=200since_id=18937297074 Don't know how to get the rest. Response= Date: Mon, 19 Jul 2010 19:34:27 GMT Server: hi Status: 200 OK X-Transaction: 1279568067-371-18115 X-Transaction: 1279568067-371-18115 X-RateLimit-Limit: 150 X-RateLimit-Limit: 150 ETag: 436458580446ee43d8d16a7f59188e7e ETag: 436458580446ee43d8d16a7f59188e7e Last-Modified: Mon, 19 Jul 2010 19:34:27 GMT Last-Modified: Mon, 19 Jul 2010 19:34:27 GMT X-RateLimit-Remaining: 143 X-RateLimit-Remaining: 143 X-Runtime: 0.05456 X-Runtime: 0.05456 Content-Type: text/html; charset=utf-8 Content-Length: 46998 Content-Length: 4659 Pragma: no-cache Pragma: no-cache X-RateLimit-Class: api X-RateLimit-Class: api X-Revision: DEV X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0 X-RateLimit-Reset: 1279570023 X-RateLimit-Reset: 1279570023 Set-Cookie: k=67.176.217.52.1279568067505660; path=/; expires=Mon, 26-Jul-10 19:34:27 GMT; domain=.twitter.com Set-Cookie: guest_id=12795680675365717; path=/; expires=Wed, 18 Aug 2010 19:34:27 GMT Set-Cookie: lang=en; path=/ Set-Cookie: _twitter_sess=BAh7CDoPY3JlYXRlZF9hdGwrCOY7M%252BwpAToHaWQiJWIxNjMxMmM2OWE0Yzg4%250AYzZiYzNkYjczY2IzOWE5NjQyIgpmbGFzaElDOidBY3Rpb25Db250cm9sbGVy%250AOjpGbGFzaDo6Rmxhc2hIYXNoewAGOgpAdXNlZHsA--9760890cd67ae21e1415b4f4fd5f04f4a1a4e876; domain=.twitter.com; path=/ Vary: Accept-Encoding Connection: close On 07/19/2010 02:53 PM, Taylor Singletary wrote: Hi Everyone, This sounds very strange. Anyone have any captures of the entire request sequence? - Your HTTP headers, including acceptance headers, the full URI being executed, etc. - The full response, including HTTP Headers (as can be provided without compromising private user / app data) Thanks! Taylor On Mon, Jul 19, 2010 at 12:36 PM, Bill Jacobson gabe...@gmail.com mailto:gabe...@gmail.com wrote: I'm expecting 'application/json' and am suddenly getting 'text/html'. On 07/19/2010 01:58 PM, Rich wrote: I'm seeing an increase in the home timeline returning a content-type of text/html instead of text/xml The actual body of the request is actually the correct XML response but my app checks for the correct HTTP header content-type. Is anyone else seeing this?
[twitter-dev] Re: Problems Connecting to the API
Desktop via Comcast, Chicago, local times: -last successful timeline call at 3:50am -one search query got a response, at 7am -no access to web site Michael D. Ivey wrote: Yes. Unable to connect via Tweetie from home (one of my traceroutes was from home) and lots of reports from iPhone, ATT and Comcast users in Southeast. Sent from my iPhone On Oct 18, 2009, at 9:56 AM, John Kalucki jkalu...@gmail.com wrote: And here's the next question: Is anyone having trouble from non-service, non-hosted endpoints. In other words, problem from home ISPs and desktop clients? -John Kalucki http://twitter.com/jkalucki Services, Twitter Inc. On Oct 18, 7:55 am, John Kalucki jkalu...@gmail.com wrote: OK. I think we have enough traceroutes for now. Thanks for sending them in! If we need more datapoints or information, I'll update this thread. On Oct 18, 7:14 am, John Kalucki jkalu...@gmail.com wrote: I don't see any operational issues from here, but I'm not an operational guy. At first glance the system looks fine, and the operational team isn't in response mode. This is puzzling. Seems like a connectivity issue upstream from twitter. At lest a few developers: please send a traceroute to this list. Also, if you aren't timing out, but rather are getting an HTTP error, send the response headers. After say 4 or 5 responses, they'll probably have enough info to triage this. -John Kaluckihttp://twitter.com/jkalucki Services, Twitter Inc. On Oct 18, 6:40 am, Dewald Pretorius dpr...@gmail.com wrote: Does anyone else have problems connecting to the API at the moment (Sunday morning October 18)? Dewald
