Maybe I missed an API update somewhere overnight, but I noticed that
http://twitter.com/statuses/user_timeline.json is no longer working.
It is returning a 301 error, (redirecting to itself :-\).
Am I missing something? Or is something on my side broken?
Thanks
On Aug 31, 9:05 am, FFMG <spambuc...@myoddweb.com> wrote:
> Hi,
>
> Maybe I missed an API update somewhere overnight, but I noticed thathttp://twitter.com/statuses/user_timeline.jsonis no longer working.
So you can authenticate and get data from that site?
BTW, mu user name and password is right.
FFMG
-
Justin Williams
Owner, Second Gear
http://www.secondgearllc.com/
--
Alex Payne
http://twitter.com/al3x
On Aug 31, 11:52 am, "Alex Payne" <a...@al3x.net> wrote:
> Last night we changed the way requests are routed from our load
> balancer to our cluster of web servers. We're still ironing out some
> kinks. The 301 is not an application-level change.
>
Thanks for the update. Is there anything I can do on my end to
alleviate the issue? Seems like some API apps (Hahlo and
Twitterrific) are working, whereas others aren't.
- j
Any news on this topic? I'm using the rss version and i still get the
301.
- Mitschi
I can logon to my Twitter account just fine. But I'm trying to see if
the plug-in has an issue or Twitter?
It was working yesterday and today, just quit. I checked again and am
getting the same error. Now I know this group isn't here to support
WordPress or my plug-ins but I am just curious if the issue above is
resolved?
If not, I can keep checking. But if it has, then I need to go back
and find out why the plug-in is not working.
On Aug 31, 3:46 pm, "Alex Payne" <a...@al3x.net> wrote:
> Not sure yet, we'll let you know.
>
Maybe it's just me, but it seems like major changes to the API are
something that should be announced to developers in some fairly
obvious way. Maybe I'm wrong.
But going to Twitter itself or using the Facebook app works just fine.
I think Twitter changed something and Alex who wrote my WordPress plug-
in doesn't see the problem yet or enough people haven't said it's
broken for him to fix it.
http://alexking.org/blog/2007/09/01/twitter-tools-broken
While he doesn't look to be pointing fingers he does say that it's
currently out of his hands. My frustration is the fact that if there
is a problem (which we all know there is) and twitter changed
something, then why didn't they (a) tell people - at least the
developers - that they were making changes and to expect some trouble
and (b) come out after the changes were made once they started hearing
that issues were arising and post something acknowledging the problem
instead of making people have to ask them.
It's not life ending, but it does suck.
It could be used in the API called on the Twitter side. Those of you
that are using the
XML instead of JSON is www included in your url to the XML file?
Kevin
> > > > > Alex Paynehttp://twitter.com/al3x- Hide quoted text -
>
> - Show quoted text -
for those still seeing 301 Redirects, please use HTTP/1.1 if possible.
We're working on getting a fix out, but as long as you're making HTTP/
1.1 requests to "twitter.com", you shouldn't see any problems.
We'll keep you posted. I hope to have this resolved within the hour.
Blaine
http://twitter.com/blaine/
On Sep 1, 12:07 pm, kda...@firehorseinvestments.com wrote:
> There was a problem mentioned on the Twitter blog with problems
> posting through
> Twitter.com itself. It may be related, since it was mentioned that a
> 301 redirect
> is occuring. If you go to any url withwww.twitter.comit redirects
> > > > > > Alex Paynehttp://twitter.com/al3x-Hide quoted text -
It appears to be working. Thank you (both Twitter and Alex) for
seeing the issue and resolving it.
On Sep 1, 12:40 pm, Blaine Cook <rom...@gmail.com> wrote:
> Hey all,
>
> for those still seeing 301 Redirects, please use HTTP/1.1 if possible.
> We're working on getting a fix out, but as long as you're making HTTP/
> 1.1 requests to "twitter.com", you shouldn't see any problems.
>
> We'll keep you posted. I hope to have this resolved within the hour.
>
> Blainehttp://twitter.com/blaine/
> > > > > > > Alex Paynehttp://twitter.com/al3x-Hidequoted text -
I've just finished confirming and I believe fixing the issue on the
twitter.side.
Previously, we did not filter incoming requests based on HTTP host:
headers.
Now, that is one of the mechanisms we use to make sure your request
get's to the right place.
Some of the API consumers appear to be sending nothing in the HTTP
host: header, while others were sending perfectly spec legitimate
host:twitter.com:80, which I had not accounted for when I configured
the filter.
Needless to say I'm very sorry for the inconvenience and happy to say
that almost all API requests are now working without redirects.
If you experience any further complications please don't hesitate to
let us know.
Jeremy
twitter operations
http://twitter.com/jeremy/
> > > > > > > > Alex Paynehttp://twitter.com/al3x-Hidequotedtext -
Yep, all working fine here
Thanks
FFMG
http://www.journalhome.com/
http://twitter.com/JournalHome/