We're discussing a local proxy that could be used for testing. It's definitely a known problem.
On Mon, Mar 9, 2009 at 12:28, Chad Etzel <jazzyc...@gmail.com> wrote: > >> What else does the community have to offer when it comes to our >> favorite API unit test framework :) > > I was just going to comment on this.... what happens when OAuth hits? > I fear that this very simple diagnostic mechanism will become > obsolete. Now asking someone to run a quick curl test becomes (I'm > assuming) more complicated. > > -Chad > > On Mon, Mar 9, 2009 at 3:25 PM, Doug Williams <d...@twitter.com> wrote: >> >> Great tip! This should become a great thread with cURL tips. >> >> Below shows how to send POST data (note the -d flag): >> >> curl -u username:password -d status="Updating with cURL" >> http://twitter.com/statuses/update.xml >> >> You can also send GET requests: >> >> curl -u username:password http://twitter.com/statuses/friends_timeline.xml >> >> >> >> Doug Williams >> Twitter API Developer Support >> http://twitter.com/dougw >> >> >> On Mon, Mar 9, 2009 at 3:14 PM, TjL <luo...@gmail.com> wrote: >>> >>> I'm not sure how many other people know this, so my apologies if this >>> is "Duh" material, but I've never worked much with curl before (always >>> been a lynx man :-) >>> >>> If you use 'curl --netrc' curl will check ~/.netrc for your Twitter >>> login information. >>> >>> Just enter your Twitter login information like this: >>> >>> machine twitter.com >>> login twitreport >>> password SuPerSEkret >>> >>> Obviously change 'twitreport' to your Twittername and 'SuPerSEkret' to >>> your password. It can all be on one line if you prefer. >>> >>> The nice thing is that this keeps your password from appearing in 'ps' >>> and you don't have to type it in each time, just add --netrc and it >>> will happen automatically. >>> >>> TjL >> > -- Alex Payne - API Lead, Twitter, Inc. http://twitter.com/al3x
