Yes, I just tried it again. URL: https://api.twitter.com/1/statuses/update.json
Headers: Date: Mon, 22 Mar 2010 21:09:39 GMT Server: hi Status: 200 OK X-Transaction: 1269292179-62279-30903 ETag: "05ef33cb30cec1cfa0c5887d4862c9df" Last-Modified: Mon, 22 Mar 2010 21:09:39 GMT X-Runtime: 0.26340 Content-Type: application/json; charset=utf-8 Content-Length: 1274 Pragma: no-cache X-Revision: DEV Expires: Tue, 31 Mar 1981 05:00:00 GMT Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post- check=0 Set-Cookie: guest_id=1269292179683; path=/ Set-Cookie: lang=en; path=/ Set-Cookie: [snipped] Vary: Accept-Encoding Connection: close The <id> and <text> returned were the latest successful tweet, not the duplicate text I was trying to post. On Mar 22, 6:08 pm, Mark McBride <mmcbr...@twitter.com> wrote: > On api.twitter.com/1/statuses/update.json? > > ---Mark > > http://twitter.com/mccv > > > > On Mon, Mar 22, 2010 at 1:58 PM, Dewald Pretorius <dpr...@gmail.com> wrote: > > When is the change going live to return a 403 response code on a > > duplicate post? > > > I'm still getting the old behavior. A 200 OK is returned with the > > details of the latest successful tweet on the account. > > > To unsubscribe from this group, send email to twitter-development-talk+ > > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > > ME" as the subject.- Hide quoted text - > > - Show quoted text - To unsubscribe from this group, send email to twitter-development-talk+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
