I have the same problem.
I've tried to not include the _method param from signature computing,
didn't work any better.
On Dec 3, 11:13 am, Wilfred yau wld991...@gmail.com wrote:
I have try that put the _method=DELETEin Header, but still not
work...
do anyone know if it is Twitter API bug or
I submitted a bug, vote for it:
http://code.google.com/p/twitter-api/issues/detail?id=1294colspec=ID%20Stars%20Type%20Status%20Priority%20Owner%20Summary%20Opened%20Modified%20Component
On Dec 3, 11:13 am, Wilfred yau wld991...@gmail.com wrote:
I have try that put the _method=DELETEin Header,
I have try that put the _method=DELETE in Header, but still not
work...
do anyone know if it is Twitter API bug or it is my problem...
this problem stop the development of my new Twitter Client in
Firefox...
Thanks
Wilfred
On Nov 27, 1:24 pm, Mark McBride mmcbr...@twitter.com wrote:
It looks
I have try to follow to OAuth document to set up Authorization header,
but still get
401 Unauthorized when I am using _method as parameter, and here is the
result:
*Response Headers
DateTue, 01 Dec 2009 03:21:03 GMT
I have already solve the special char problem because encoding in
Flex.
but I still find that when I call _method= DELETE in List API, I still
get 401 Unauthorized from api.twitter.com.
On Nov 25, 11:09 am, Wilfred yau wld991...@gmail.com wrote:
I am using OAuth to accessListAPI, but I find that
It looks like you're trying to actually include the OAuth
Authorization header in your POST body, which isn't the way you want
to do it. Instead, you should be using the Authorization HTTP header
to transmit this info (see http://oauth.net/core/1.0a#anchor46). To
make things extra weird, in one
