The problem was reported by one of our users, but when I tested our
software with my own Twitter account - which is alive and in good
standing - I got the same 404 message.
If I use 'curl', i.e.
curl -u user:pass http://twitter.com/statuses/user_timeline.json
It works fine. However, if I use the Perl Net::Twitter equivalent,
i.e.
use Net::Twitter;
my $twitter = Net::Twitter->new(username => "user", password =>
"pass");
my $timeline = $twitter->user_timeline({ count => 1 });
print $twitter->http_code, " ", $twitter->http_message();
I get the 404 Not Found error.
Both my simple Net::Twitter test case and our actual application have
worked well in the past, and our Net::Twitter module is up-to-date.
Is it possible that Twitter's behavior depends in some way on other
headers sent by the client?
Thanks for your help,
Angus
On Oct 17, 9:44 pm, "Alex Payne" <[EMAIL PROTECTED]> wrote:
> Nope, hasn't changed. Is it possible that the user you're requesting
> was deleted or marked as a spammer?
>
> On Fri, Oct 17, 2008 at 3:48 PM, angusmci <[EMAIL PROTECTED]> wrote:
>
> > A part of our app that made use of the '/statuses/
> > user_timeline.format' endpoint has broken, and tests show that we're
> > now getting a 404 result from that (using 'curl', or the Perl
> > Net::Twitter module).
>
> > Has the API changed recently?
>
> > Angus
>
> --
> Alex Payne - API Lead, Twitter, Inc.http://twitter.com/al3x
