I've got the same issue, started today when it worked fine yesterday

On May 21, 3:48 am, Abraham Williams <4bra...@gmail.com> wrote:
> Can you confirm if post_statusesUpdate() works without the
> 'in_reply_to_status_id' parameter?
>
> 2009/5/19 alon <alon.car...@gmail.com>
>
>
>
>
>
> > Hello all! ,Jaisen,
> > I'm trying to use your EpiTwitter php class to communicate with the
> > twitter API.
>
> > This is my php code:
>
> > $twitterObj = new EpiTwitter($consumer_key, $consumer_secret,
> > USER_TOKEN, USER_SECRET_TOKEN);
> > $userInfo = $twitterObj->get_accountVerify_credentials();
> > $twitterObj->post_statusesUpdate(array("status" => $status,
> > "in_reply_to_status_id" => $replytoid));
>
> > The first request (acount/verify_credential) returns fine, following
> > is the http request:
>
> > GET /account/verify_credentials.json HTTP/1.1
>
> > Host: twitter.com
>
> > Accept: */*
>
> > Authorization: OAuth realm="/account/
>
> > verify_credentials.json",oauth_consumer_key="XXXX",oauth_token="XXXX",oauth_nonce="XXXXXX",oauth_timestamp="1242578551",oauth_signature_method="HMAC-
> > SHA1",oauth_version="1.0",oauth_signature="XXXX"
>
> > The second request (statuses/update) returns with "Failed to validate
> > oauth signature or token" :
>
> > POST /statuses/update.json HTTP/1.1
>
> > Host: twitter.com
>
> > Accept: */*
>
> > Authorization: OAuth realm="/statuses/
>
> > update.json",oauth_consumer_key="XXXX",oauth_token="XXXXX",oauth_nonce="XXXX",oauth_timestamp="1242578551",oauth_signature_method="HMAC-
> > SHA1",oauth_version="1.0",oauth_signature="XXXX"
>
> > Content-Length: 81
>
> > Content-Type: application/x-www-form-urlencoded
>
> > status=%40LeeronShalev+testing%3A+One%2C
> > +Two&amp;in_reply_to_status_id=1786937496
>
> > Thanks in advance,
>
> --
> Abraham Williams |http://the.hackerconundrum.com
> Hacker |http://abrah.am|http://twitter.com/abraham
> Web608 | Community Evangelist |http://web608.org
> This email is: [ ] blogable [x] ask first [ ] private.
> Sent from San Francisco, California, United States

Reply via email to