Hi Ted, I think it's unlikely that we're throwing the actual 424 in this case. Do you know much about your production environment and what kinds of proxies you go through?
Taylor Singletary Developer Advocate, Twitter http://twitter.com/episod On Fri, May 21, 2010 at 10:45 AM, ted <[email protected]> wrote: > I'm experimenting with the Twitter API (OAuth). I have a test bed that > can tweet from my dev PC and my staging PC, but it fails on my > production server. I get a status code of 424 returned when trying to > tweet. > > I can't spot any differences between the environments that might be > instrumental. > > I've not found any info on the 424 error other than references to > WebDav and it being an error related to a previous call. > > The call I'm making it the first one and I used a hard coded token and > secret token when tweeting. > > I'm stumped and any help would be greatly appreciated! > > TIA > Ted >
