(400) Bad Request error with admin feed (twitter)


There are error log entries like this every hour (v1.3b):
The feed twitter.com/.../graffiticms.rss (Name:Feed:http://twitter.com/statuses/user_timeline/graffiticms.rss Id:95d2b007-faa4-41e8-8bc8-0c7c15778552 was not successfully updated. Reason: The remote server returned an error: (400) Bad Request.
According to this answer (http://stackoverflow.com/questions/4060876/why-is-this-twitter-api-script-failing) it seems to be related to the twitter "rate limiting" (https://dev.twitter.com/docs/rate-limiting).
I looked into the code for 1.3b, and there is a hardcoded 60 minutes interval that seems to be way too small. So to get around I have to wait for a fix..., no config open I can change other than "ignore/remove" the admin twitter feed usage at all?


jkillebrew wrote Apr 14, 2012 at 4:34 AM

I've never seen this on my twitter feeds and the timeout is large enough that the 60 minute intervals should not trigger the rate limiting if rate limiting even exists on twitter rss. It could be that you are accessing the feed in other ways outside this one graffiti site from the same server and triggering the rate limit. You might try flushing the rss feeds out of graffiti. You can do this from Site options - utilities - rebuild pages -flush rss feeds

wrote Feb 14, 2013 at 7:43 PM

jkillebrew wrote May 11, 2013 at 6:25 AM

Upon close inspection, it appears that the rss feed you mentioned is the old api which is deprecated and is no longer available. Instead the correct url is https://api.twitter.com/1/statuses/user_timeline.rss?screen_name=graffiticms which was fixed in the source recently and will be included in the next release.

The fix was applied at Change set 96007, Nov 10, 2012

If and when you update to a newer version, the errors will not go away until you flush the rss feeds as I mentioned, because even if those feeds are no longer needed, graffiti seems to hold on to them forever.

wrote May 11, 2013 at 6:25 AM

wrote May 16, 2013 at 9:38 AM

wrote May 16, 2013 at 9:38 AM

wrote Jun 14, 2013 at 7:16 AM

TorstenR wrote Jan 8, 2014 at 12:01 PM

Problem still persists. Errors are reported on two sites I run with Graffiti:


The feed api.twitter.com/.../user_timeline.r (Name:Feed:https://api.twitter.com/1/statuses/user_timeline.rss?screen_name=graffiticms Id:d274810f-3a6d-4824-97bc-44d69b267e3c was not successfully updated. Reason: The remote server returned an error: (410) Gone.