[twitter-dev] Re: 401 Unauthorized problem
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 wrote:
> 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 (seehttp://oauth.net/core/1.0a#anchor46). To
> make things extra weird, in one case you do have an Authorization
> header set, but it's basic auth.
>
> ---Mark
>
> On Thu, Nov 26, 2009 at 6:47 PM, Wilfred yau wrote:
> > 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 wrote:
> >> I am using OAuth to accessListAPI, but I find that if the request
> >> URL contain some char like "_", "(", then twitter will return 401
> >> Unauthorized.
>
> >> Does anyone know what is the problem??
>
> >> and this is my request:
>
> >> *Request URL:
>
> >>http://api.twitter.com/1/wilfred_yau/yedsrc/members.xml
>
> >> *Request header:
>
> >> Host:api.twitter.com
> >> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:
> >> 1.9.2b3) Gecko/20091115 Firefox/3.6b3 GTB6
> >> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/
> >> *;q=0.8
> >> Accept-Language: en-us,en;q=0.5
> >> Accept-Encoding: gzip,deflate
> >> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> >> Keep-Alive: 115
> >> Connection: keep-alive
> >> Cookie: __utma=43838368.448377351.1258538849.1259115844.1259117264.22;
> >> __utmz=43838368.1258703218.9.4.utmcsr=google|utmccn=(organic)|
> >> utmcmd=organic|utmctr=gmasbaby; __utmv=43838368.lang%3A%20en;
> >> __qca=P0-1731751766-1258598366235; __utmb=43838368.8.10.1259117264;
> >> _twitter_sess=BAh7DDoTcGFzc3dvcmRfdG9rZW4iLWYxZDlkMzA5OWExZTMxMDIzZTlmMGJj
> >> %250AOWM1YzllYzAyYTVjOWU2NGM6DGNzcmZfaWQiJTU4MTVlMjgzNWUyNGNhYThh
> >> %250ANjE1YzdjOWU4MTE5MGJjOhF0cmFuc19wcm9tcHQwOgl1c2VyaQQ5oOgDOg5y
> >> %250AZXR1cm5fdG8iJGh0dHA6Ly90d2l0dGVyLmNvbS9zb2Z0cGVkaWFtYWM6B2lk
> >> %250AIiU0Y2JmMWJmNjc0YzJmOTlhZGZjMTA1MzE3NzI3ZGUwNiIKZmxhc2hJQzon
> >> %250AQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7%250AAA
> >> %253D%253D--3573176707558a7f9cd9653e6a60c073c94e91f5; __utmc=43838368
>
> >> *Post Data:
> >> Content-type: application/x-www-form-urlencoded
> >> Content-length: 300
>
> >> oauth%5Fconsumer%5Fkey=WiW3RrjmAhPvWvTn6oPLA&id=66626470&oauth
> >> %5Ftoken=65577017%2DK65DjHAcUbYOEJW5XMVnVuAkRy8fDnNnVGRZDOSAQ&oauth
> >> %5Ftimestamp=1259118273&oauth%5Fsignature=zaA0CbWpls3lowiWG0yHCZig%2B2M
> >> %3D&oauth%5Fversion=1%2E0&oauth%5Fsignature%5Fmethod=HMAC%2DSHA1&
> >> %5Fmethod=DELETE&oauth%5Fnonce=2875
>
> >> Also, I got same problem in set status using OAuth :
>
> >> *Request URL:
>
> >>http://twitter.com/statuses/update.xml
>
> >> *Request header:
>
> >> Host: twitter.com
> >> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:
> >> 1.9.2b3) Gecko/20091115 Firefox/3.6b3 GTB6
> >> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/
> >> *;q=0.8
> >> Accept-Language: en-us,en;q=0.5
> >> Accept-Encoding: gzip,deflate
> >> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> >> Keep-Alive: 115
> >> Connection: keep-alive
> >> Cookie: __utma=43838368.448377351.1258538849.1259115844.1259117264.22;
> >> __utmz=43838368.1258703218.9.4.utmcsr=google|utmccn=(organic)|
> >> utmcmd=organic|utmctr=gmasbaby; __utmv=43838368.lang%3A%20en;
> >> __qca=P0-1731751766-1258598366235; __utmb=43838368.8.10.1259117264;
> >> _twitter_sess=BAh7DDoTcGFzc3dvcmRfdG9rZW4iLWYxZDlkMzA5OWExZTMxMDIzZTlmMGJj
> >> %250AOWM1YzllYzAyYTVjOWU2NGM6DGNzcmZfaWQiJTU4MTVlMjgzNWUyNGNhYThh
> >> %250ANjE1YzdjOWU4MTE5MGJjOgl1c2VyaQQ5oOgDOhF0cmFuc19wcm9tcHQwIgpm
> >> %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG
> >> %250AOgpAdXNlZHsAOgdpZCIlNGNiZjFiZjY3NGMyZjk5YWRmYzEwNTMxNzcyN2Rl
> >> %250AMDY6DnJldHVybl90byIkaHR0cDovL3R3aXR0ZXIuY29tL3NvZnRwZWRpYW1h
> >> %250AYw%253D%253D--dfa30d93e80be97e1404abbb466f2c6191816d69;
> >> __utmc=43838368
> >> Authorization: Basic Z21hc2JhYnk6eW95b2JhYnk=
>
> >> *Post Data:
>
> >> Content-type: application/x-www-form-urlencoded
> >> Content-length: 303
>
> >> oauth%5Fnonce=4280&oauth%5Fsignature%5Fmethod=HMAC%2DSHA1&oauth
> >> %5Ftimestamp=1259117789&status=%40vincenthpchan%20%28O%3A&oauth
> >> %5Fversion=1%2E0&oauth%5Fconsumer%5Fkey=WiW3RrjmAhPvWvTn6oPLA&oauth
> >> %5Fsignature=dZ0OBySJzAZsdhwUKvK9zaIamE4%3D&oauth
> >> %5Ftoken=65577017%2DK65DjHAcUbYOEJW5XMVnVuAkRy8fDnNnVGRZDOSAQ
>
> >> I wonder it is the problem about oauth_signature, but I don't what
> >> wrong with it.
> >> Thanks you very much ;-)
[twitter-dev] Re: 401 Unauthorized problem
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
Server hi
WWW-AuthenticateBasic realm="Twitter API"
Status 401 Unauthorized
Content-Typeapplication/xml; charset=utf-8
Cache-Control no-cache, max-age=1800
Set-Cookie
_twitter_sess=BAh7CjoTcGFzc3dvcmRfdG9rZW4iLWYxZDlkMzA5OWExZTMxMDIzZTlmMGJj
%250AOWM1YzllYzAyYTVjOWU2NGM6CXVzZXJpBDmg6AM6EXRyYW5zX3Byb21wdDAi
%250ACmZsYXNoSUM6J0FjdGlvbkNvbnRyb2xsZXI6OkZsYXNoOjpGbGFzaEhhc2h7%250AAAY6CkB1c2VkewA6B2lkIiU5ZWI2NmY2MTU5ZmYyODM4NGE3YTAxNGUxMmMy
%250AMTAyNg%253D%253D--4353873c14c39b48b0d30c48abba5858bff5a3a0;
domain=.twitter.com; path=/
Expires Tue, 01 Dec 2009 03:51:03 GMT
VaryAccept-Encoding
Content-Encodinggzip
Content-Length 140
Connection close
*Request Headers
Hostapi.twitter.com
User-Agent Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.5)
Gecko/20091102 Firefox/3.5.5 GTB6
Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language en-us,en;q=0.5
Accept-Encoding gzip,deflate
Accept-Charset ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive 300
Connection keep-alive
Cookie __qca=P0-1306444636-1259550182670;
__utma=43838368.345398731.1259564074.1259574616.1259577218.3;
__utmz=43838368.1259577218.3.2.utmcsr=forum7.hkgolden.com|utmccn=
(referral)|utmcmd=referral|utmcct=/view.aspx; __utmv=43838368.lang%3A
%20en;
_twitter_sess=BAh7CjoTcGFzc3dvcmRfdG9rZW4iLWYxZDlkMzA5OWExZTMxMDIzZTlmMGJj
%250AOWM1YzllYzAyYTVjOWU2NGM6EXRyYW5zX3Byb21wdDA6CXVzZXJpBDmg6AM6%250AB2lkIiU5ZWI2NmY2MTU5ZmYyODM4NGE3YTAxNGUxMmMyMTAyNiIKZmxhc2hJ
%250AQzonQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVz
%250AZWR7AA%253D%253D--00951782ee94404e73d0edcbd7d02f1800f10915
*Post Data:
Content-type: application/x-www-form-urlencoded
Authorization: OAuth realm="Test",oauth_signature_method="HMAC-
SHA1",oauth_token="65577017-
K65DjHAcUbYOEJW5XMVnVuAkRy8fDnNnVGRZDOSAQ",oauth_nonce="9399",oauth_timestamp="1259637691",oauth_version="1.0",oauth_consumer_key="WiW3RrjmAhPvWvTn6oPLA",oauth_signature="BhLQP0o0OKLXjiQWn1l9ca7Fsek
%3D"
Content-length: 28
id=77938855&%5Fmethod=DELETE
I wonder this the the problem of _method since when I use other
parameter, there are no problem at all. So, do anyone know what is the
problem of my request and could twitter provide a correct Request
example which using _method as a OAuth parameter? Thanks.
Wilfred
On Nov 27, 1:24 pm, Mark McBride wrote:
> 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 (seehttp://oauth.net/core/1.0a#anchor46). To
> make things extra weird, in one case you do have an Authorization
> header set, but it's basic auth.
>
> ---Mark
>
> On Thu, Nov 26, 2009 at 6:47 PM, Wilfred yau wrote:
> > I have already solve the special char problem because encoding in
> > Flex.
> > but I still find that when I call _method= DELETE inListAPI, I still
> > get 401 Unauthorized from api.twitter.com.
>
> > On Nov 25, 11:09 am, Wilfred yau wrote:
> >> I am using OAuth to accessListAPI, but I find that if the request
> >> URL contain some char like "_", "(", then twitter will return 401
> >> Unauthorized.
>
> >> Does anyone know what is the problem??
>
> >> and this is my request:
>
> >> *Request URL:
>
> >>http://api.twitter.com/1/wilfred_yau/yedsrc/members.xml
>
> >> *Request header:
>
> >> Host:api.twitter.com
> >> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:
> >> 1.9.2b3) Gecko/20091115 Firefox/3.6b3 GTB6
> >> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/
> >> *;q=0.8
> >> Accept-Language: en-us,en;q=0.5
> >> Accept-Encoding: gzip,deflate
> >> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> >> Keep-Alive: 115
> >> Connection: keep-alive
> >> Cookie: __utma=43838368.448377351.1258538849.1259115844.1259117264.22;
> >> __utmz=43838368.1258703218.9.4.utmcsr=google|utmccn=(organic)|
> >> utmcmd=organic|utmctr=gmasbaby; __utmv=43838368.lang%3A%20en;
> >> __qca=P0-1731751766-1258598366235; __utmb=43838368.8.10.1259117264;
> >> _twitter_sess=BAh7DDoTcGFzc3dvcmRfdG9rZW4iLWYxZDlkMzA5OWExZTMxMDIzZTlmMGJj
> >> %250AOWM1YzllYzAyYTVjOW
[twitter-dev] OAuth DELETE LIST problem
Hello all, When I call _method= DELETE in List API, I got 401 Unauthorized from api.twitter.com. After I read the document of OAuth, it mention that "_" is no need to encode so it may be a another problem. I have try when I using other parameter include "_" like "a_method=DELETE" is work well and return 200 OK, So, I wound it is the problem in server side?? I can't develop in my twitter Client using Flex in FireFox more since this problem ,can any twitter support team member help me to find out what is the problem?? or any people can success use _method as parameter in Oauth can provide solution for me?? Thanks. Wilfred
[twitter-dev] Re: 401 Unauthorized problem
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 wrote:
> I am using OAuth to accessListAPI, but I find that if the request
> URL contain some char like "_", "(", then twitter will return 401
> Unauthorized.
>
> Does anyone know what is the problem??
>
> and this is my request:
>
> *Request URL:
>
> http://api.twitter.com/1/wilfred_yau/yedsrc/members.xml
>
> *Request header:
>
> Host:api.twitter.com
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:
> 1.9.2b3) Gecko/20091115 Firefox/3.6b3 GTB6
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/
> *;q=0.8
> Accept-Language: en-us,en;q=0.5
> Accept-Encoding: gzip,deflate
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Keep-Alive: 115
> Connection: keep-alive
> Cookie: __utma=43838368.448377351.1258538849.1259115844.1259117264.22;
> __utmz=43838368.1258703218.9.4.utmcsr=google|utmccn=(organic)|
> utmcmd=organic|utmctr=gmasbaby; __utmv=43838368.lang%3A%20en;
> __qca=P0-1731751766-1258598366235; __utmb=43838368.8.10.1259117264;
> _twitter_sess=BAh7DDoTcGFzc3dvcmRfdG9rZW4iLWYxZDlkMzA5OWExZTMxMDIzZTlmMGJj
> %250AOWM1YzllYzAyYTVjOWU2NGM6DGNzcmZfaWQiJTU4MTVlMjgzNWUyNGNhYThh
> %250ANjE1YzdjOWU4MTE5MGJjOhF0cmFuc19wcm9tcHQwOgl1c2VyaQQ5oOgDOg5y
> %250AZXR1cm5fdG8iJGh0dHA6Ly90d2l0dGVyLmNvbS9zb2Z0cGVkaWFtYWM6B2lk
> %250AIiU0Y2JmMWJmNjc0YzJmOTlhZGZjMTA1MzE3NzI3ZGUwNiIKZmxhc2hJQzon
> %250AQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7%250AAA
> %253D%253D--3573176707558a7f9cd9653e6a60c073c94e91f5; __utmc=43838368
>
> *Post Data:
> Content-type: application/x-www-form-urlencoded
> Content-length: 300
>
> oauth%5Fconsumer%5Fkey=WiW3RrjmAhPvWvTn6oPLA&id=66626470&oauth
> %5Ftoken=65577017%2DK65DjHAcUbYOEJW5XMVnVuAkRy8fDnNnVGRZDOSAQ&oauth
> %5Ftimestamp=1259118273&oauth%5Fsignature=zaA0CbWpls3lowiWG0yHCZig%2B2M
> %3D&oauth%5Fversion=1%2E0&oauth%5Fsignature%5Fmethod=HMAC%2DSHA1&
> %5Fmethod=DELETE&oauth%5Fnonce=2875
>
> Also, I got same problem in set status using OAuth :
>
> *Request URL:
>
> http://twitter.com/statuses/update.xml
>
> *Request header:
>
> Host: twitter.com
> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:
> 1.9.2b3) Gecko/20091115 Firefox/3.6b3 GTB6
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/
> *;q=0.8
> Accept-Language: en-us,en;q=0.5
> Accept-Encoding: gzip,deflate
> Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
> Keep-Alive: 115
> Connection: keep-alive
> Cookie: __utma=43838368.448377351.1258538849.1259115844.1259117264.22;
> __utmz=43838368.1258703218.9.4.utmcsr=google|utmccn=(organic)|
> utmcmd=organic|utmctr=gmasbaby; __utmv=43838368.lang%3A%20en;
> __qca=P0-1731751766-1258598366235; __utmb=43838368.8.10.1259117264;
> _twitter_sess=BAh7DDoTcGFzc3dvcmRfdG9rZW4iLWYxZDlkMzA5OWExZTMxMDIzZTlmMGJj
> %250AOWM1YzllYzAyYTVjOWU2NGM6DGNzcmZfaWQiJTU4MTVlMjgzNWUyNGNhYThh
> %250ANjE1YzdjOWU4MTE5MGJjOgl1c2VyaQQ5oOgDOhF0cmFuc19wcm9tcHQwIgpm
> %250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG
> %250AOgpAdXNlZHsAOgdpZCIlNGNiZjFiZjY3NGMyZjk5YWRmYzEwNTMxNzcyN2Rl
> %250AMDY6DnJldHVybl90byIkaHR0cDovL3R3aXR0ZXIuY29tL3NvZnRwZWRpYW1h
> %250AYw%253D%253D--dfa30d93e80be97e1404abbb466f2c6191816d69;
> __utmc=43838368
> Authorization: Basic Z21hc2JhYnk6eW95b2JhYnk=
>
> *Post Data:
>
> Content-type: application/x-www-form-urlencoded
> Content-length: 303
>
> oauth%5Fnonce=4280&oauth%5Fsignature%5Fmethod=HMAC%2DSHA1&oauth
> %5Ftimestamp=1259117789&status=%40vincenthpchan%20%28O%3A&oauth
> %5Fversion=1%2E0&oauth%5Fconsumer%5Fkey=WiW3RrjmAhPvWvTn6oPLA&oauth
> %5Fsignature=dZ0OBySJzAZsdhwUKvK9zaIamE4%3D&oauth
> %5Ftoken=65577017%2DK65DjHAcUbYOEJW5XMVnVuAkRy8fDnNnVGRZDOSAQ
>
> I wonder it is the problem about oauth_signature, but I don't what
> wrong with it.
> Thanks you very much ;-)
[twitter-dev] Re: Twitter login with Flex
I think you are using Basic Auth to login, but it don't work well in Flex, you should try to use OAuth that have better support on Flex. any you can use some library to help you finish the project: http://code.google.com/p/tweetr/ http://code.google.com/p/oauth-as3/ sample code is including in the library. On Nov 26, 9:27 pm, Jef wrote: > Hey guys > > I'm building an application for a school project where I should be > able to do everything you can on Twitter.com, but make it accessible > on the desktop (AIR project) > But I have absolutely no clue how I can login as a user and update my > status. I've looked at the API documentation, but so far it's been > nothing but Chinese to me :P > Retrieving search information and other timelines is no problem > though, it's just the status update part that's been bothering me :D > > I'd love to get some help on this. > > Thanks in advance! > > Jef
[twitter-dev] [OAuth + LIST API ] 401 Unauthorized problem
I am using OAuth to access List API, but I find that if the request
URL contain some char like "_", "(", then twitter will return 401
Unauthorized.
Does anyone know what is the problem??
and this is my request:
*Request URL:
http://api.twitter.com/1/wilfred_yau/yedsrc/members.xml
*Request header:
Host: api.twitter.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:
1.9.2b3) Gecko/20091115 Firefox/3.6b3 GTB6
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/
*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Cookie: __utma=43838368.448377351.1258538849.1259115844.1259117264.22;
__utmz=43838368.1258703218.9.4.utmcsr=google|utmccn=(organic)|
utmcmd=organic|utmctr=gmasbaby; __utmv=43838368.lang%3A%20en;
__qca=P0-1731751766-1258598366235; __utmb=43838368.8.10.1259117264;
_twitter_sess=BAh7DDoTcGFzc3dvcmRfdG9rZW4iLWYxZDlkMzA5OWExZTMxMDIzZTlmMGJj
%250AOWM1YzllYzAyYTVjOWU2NGM6DGNzcmZfaWQiJTU4MTVlMjgzNWUyNGNhYThh
%250ANjE1YzdjOWU4MTE5MGJjOhF0cmFuc19wcm9tcHQwOgl1c2VyaQQ5oOgDOg5y
%250AZXR1cm5fdG8iJGh0dHA6Ly90d2l0dGVyLmNvbS9zb2Z0cGVkaWFtYWM6B2lk
%250AIiU0Y2JmMWJmNjc0YzJmOTlhZGZjMTA1MzE3NzI3ZGUwNiIKZmxhc2hJQzon
%250AQWN0aW9uQ29udHJvbGxlcjo6Rmxhc2g6OkZsYXNoSGFzaHsABjoKQHVzZWR7%250AAA
%253D%253D--3573176707558a7f9cd9653e6a60c073c94e91f5; __utmc=43838368
*Post Data:
Content-type: application/x-www-form-urlencoded
Content-length: 300
oauth%5Fconsumer%5Fkey=WiW3RrjmAhPvWvTn6oPLA&id=66626470&oauth
%5Ftoken=65577017%2DK65DjHAcUbYOEJW5XMVnVuAkRy8fDnNnVGRZDOSAQ&oauth
%5Ftimestamp=1259118273&oauth%5Fsignature=zaA0CbWpls3lowiWG0yHCZig%2B2M
%3D&oauth%5Fversion=1%2E0&oauth%5Fsignature%5Fmethod=HMAC%2DSHA1&
%5Fmethod=DELETE&oauth%5Fnonce=2875
Also, I got same problem in set status using OAuth :
*Request URL:
http://twitter.com/statuses/update.xml
*Request header:
Host: twitter.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:
1.9.2b3) Gecko/20091115 Firefox/3.6b3 GTB6
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/
*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Connection: keep-alive
Cookie: __utma=43838368.448377351.1258538849.1259115844.1259117264.22;
__utmz=43838368.1258703218.9.4.utmcsr=google|utmccn=(organic)|
utmcmd=organic|utmctr=gmasbaby; __utmv=43838368.lang%3A%20en;
__qca=P0-1731751766-1258598366235; __utmb=43838368.8.10.1259117264;
_twitter_sess=BAh7DDoTcGFzc3dvcmRfdG9rZW4iLWYxZDlkMzA5OWExZTMxMDIzZTlmMGJj
%250AOWM1YzllYzAyYTVjOWU2NGM6DGNzcmZfaWQiJTU4MTVlMjgzNWUyNGNhYThh
%250ANjE1YzdjOWU4MTE5MGJjOgl1c2VyaQQ5oOgDOhF0cmFuc19wcm9tcHQwIgpm
%250AbGFzaElDOidBY3Rpb25Db250cm9sbGVyOjpGbGFzaDo6Rmxhc2hIYXNoewAG
%250AOgpAdXNlZHsAOgdpZCIlNGNiZjFiZjY3NGMyZjk5YWRmYzEwNTMxNzcyN2Rl
%250AMDY6DnJldHVybl90byIkaHR0cDovL3R3aXR0ZXIuY29tL3NvZnRwZWRpYW1h
%250AYw%253D%253D--dfa30d93e80be97e1404abbb466f2c6191816d69;
__utmc=43838368
Authorization: Basic Z21hc2JhYnk6eW95b2JhYnk=
*Post Data:
Content-type: application/x-www-form-urlencoded
Content-length: 303
oauth%5Fnonce=4280&oauth%5Fsignature%5Fmethod=HMAC%2DSHA1&oauth
%5Ftimestamp=1259117789&status=%40vincenthpchan%20%28O%3A&oauth
%5Fversion=1%2E0&oauth%5Fconsumer%5Fkey=WiW3RrjmAhPvWvTn6oPLA&oauth
%5Fsignature=dZ0OBySJzAZsdhwUKvK9zaIamE4%3D&oauth
%5Ftoken=65577017%2DK65DjHAcUbYOEJW5XMVnVuAkRy8fDnNnVGRZDOSAQ
I wonder it is the problem about oauth_signature, but I don't what
wrong with it.
Thanks you very much ;-)
[twitter-dev] [bug] GET list statuses rate limit
When I testing List API, I reach the API limit but I find that I still can call "GET /:user/lists/:list_id/statuses" without any problem or Error. API document say it is limited in 150 call but I can request more. Does this call not limited by API rate? or just a bug? Since I want to use this call to check if the list updated but 150 is not enough to do this. Thanks.
[twitter-dev] Re: Draft of List API documentation
I have try this and It's work, thank you =] On Nov 4, 7:16 am, Marcel Molina wrote: > A work around for environments that don't support theDELETErequest > method is, I believe, to pass a parameter called _method with the > value "DELETE". In other words "_method=DELETE". > > > > On Mon, Nov 2, 2009 at 11:26 PM, wilfred yau wrote: > > > It there any method todeleteuser from list other then usingDELETE > > method? > > Since I am using Flex (but not Air) to develop third party Twitter > > Client, There are no way to call "DELETE" (which only GET and POST). > > So, will twitter provide POST or GET method API to "delete"? Thanks > > > On Oct 16, 3:04 pm, Marcel Molina wrote: > >> Hey folks. As some of you have likely read we're starting to do some > >> private beta testing of our new lists feature. We're not quite ready > >> to open it up to everyone but we've made some headway on the API and > >> wanted to share some details of what we've got so far. > > >> There are a handful of things on our todo lists so don't consider this > >> signed and sealed just yet. > > >> You may notice this API is a bit of a departure from the rest of the > >> API. It's a bit more, errr, REST than the rest. > > >> First off, here's the current payload for alist: > > >> > >> > >> 1416 > >> tall people > >> @noradio/tall-people > >> tall-people > >> 0 > >> 3 > >> /noradio/tall-people > >> public > >> > >> 3191321 > >> Marcel Molina > >> noradio > >> San Francisco, CA > >> Engineer at Twitter on the @twitterapi team, obsessed > >> with rock climbing & running. In a past life I was a member of the > >> Rails Core team. > >> > >> http://a3.twimg.com/profile_images/53473799/marcel-euro-rails-conf_no... > >> http://project.ioni.st > >> false > >> 40059 > >> 9AE4E8 > >> 33 > >> 0084B4 > >> DDFFCC > >> BDDCAD > >> 354 > >> Mon Apr 02 07:47:28 + 2007 > >> 131 > >> -28800 > >> Pacific Time (US & Canada) > >> > >> http://a1.twimg.com/profile_background_images/18156348/jessica_tiled > >> true > >> 3472 > >> false > >> true > >> false > >> false > >> > >> > > >> === Lists === > > >> POST '/:user/lists.:format' > >> Creates a newlistfor the authenticated user. > > >> Parameters: > >> * name: the name of thelist. (required) > >> * mode: whether yourlistis public of private. Values can be > >> 'public' or 'private'. Public by default if not specified. (optional) > > >> Usage notes: > >> ":user" in the url should be the screen name of the user making the > >> request to create thelist > > >> Supported formats: > >> xml, json > > >> e.g. > >> curl -u USERNAME:PASSWORD -d "name=tall > >> people&mode=private"http://twitter.com/noradio/lists.xml > > >> POST/PUT '/:user/lists/:list_slug.:format' > >> Updates the specifiedlist. > > >> Takes the same parameters as the create resource at POST > >> '/:user/lists.:format' (:name and :mode). > > >> Supported formats: > >> xml, json > > >> e.g. > >> curl -u USERNAME:PASSWORD -d > >> "name=giants&mode=public"http://twitter.com/noradio/lists/tall-people.xml > > >> GET '/:user/lists.:format' > >> Lists your lists. > > >> Supported format: > >> xml, json > > >> e.g. > >> curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists.xml > > >> GET '/:user/lists/memberships.:format'Listthe lists the specified user has > >> been added to. > > >> Supported formats: > >> xml, json > > >> e.g. > >> curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/memberships.xml > > >>DELETE'/:user/lists/:list_slug.:format' > >>Deletethe specifiedlistowned by the authenticated user. > > >> Parameters: > >> * list_slug: the slug of thelistyou want todelete. (required) > > >> Supported formats: > >> xml, json &g
[twitter-dev] Re: Draft of List API documentation
It there any method to delete user from list other then using DELETE method? Since I am using Flex (but not Air) to develop third party Twitter Client, There are no way to call "DELETE" (which only GET and POST). So, will twitter provide POST or GET method API to "delete"? Thanks On Oct 16, 3:04 pm, Marcel Molina wrote: > Hey folks. As some of you have likely read we're starting to do some > private beta testing of our new lists feature. We're not quite ready > to open it up to everyone but we've made some headway on the API and > wanted to share some details of what we've got so far. > > There are a handful of things on our todo lists so don't consider this > signed and sealed just yet. > > You may notice this API is a bit of a departure from the rest of the > API. It's a bit more, errr, REST than the rest. > > First off, here's the current payload for alist: > > > > 1416 > tall people > @noradio/tall-people > tall-people > 0 > 3 > /noradio/tall-people > public > > 3191321 > Marcel Molina > noradio > San Francisco, CA > Engineer at Twitter on the @twitterapi team, obsessed > with rock climbing & running. In a past life I was a member of the > Rails Core team. > > http://a3.twimg.com/profile_images/53473799/marcel-euro-rails-conf_no... > http://project.ioni.st > false > 40059 > 9AE4E8 > 33 > 0084B4 > DDFFCC > BDDCAD > 354 > Mon Apr 02 07:47:28 + 2007 > 131 > -28800 > Pacific Time (US & Canada) > > http://a1.twimg.com/profile_background_images/18156348/jessica_tiled > true > 3472 > false > true > false > false > > > > === Lists === > > POST '/:user/lists.:format' > Creates a newlistfor the authenticated user. > > Parameters: > * name: the name of thelist. (required) > * mode: whether yourlistis public of private. Values can be > 'public' or 'private'. Public by default if not specified. (optional) > > Usage notes: > ":user" in the url should be the screen name of the user making the > request to create thelist > > Supported formats: > xml, json > > e.g. > curl -u USERNAME:PASSWORD -d "name=tall > people&mode=private"http://twitter.com/noradio/lists.xml > > POST/PUT '/:user/lists/:list_slug.:format' > Updates the specifiedlist. > > Takes the same parameters as the create resource at POST > '/:user/lists.:format' (:name and :mode). > > Supported formats: > xml, json > > e.g. > curl -u USERNAME:PASSWORD -d > "name=giants&mode=public"http://twitter.com/noradio/lists/tall-people.xml > > GET '/:user/lists.:format' > Lists your lists. > > Supported format: > xml, json > > e.g. > curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists.xml > > GET '/:user/lists/memberships.:format'Listthe lists the specified user has > been added to. > > Supported formats: > xml, json > > e.g. > curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/memberships.xml > > DELETE '/:user/lists/:list_slug.:format' > Delete the specifiedlistowned by the authenticated user. > > Parameters: > * list_slug: the slug of thelistyou want to delete. (required) > > Supported formats: > xml, json > > e.g. > curl -u USERNAME:PASSWORD -X > DELETEhttp://twitter.com/noradio/lists/tall-people.xml > > GET '/:users/lists/:list_slug/statuses.:format' > Show tweet timeline for members of the specifiedlist. > > Parameters: > * list_slug: the slug of thelistyou want the member tweet timeline > of. (required) > * next/previous_cursor: used to "page" through results (optional) > > Supported formats: > xml, json > > e.g. > curl -u > USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall-people/statuses.xml > > GET '/:users/lists/:list_slug.:format' > Show a specificlistyou can use the new resource. > > Supported formats: > xml, json > > e.g. > curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/lists/tall-people.xml > > ===Listmembers === > > POST '/:user/:list_slug/members.:format' > Add a member to alist. > > Parameters: > * id: the id of the user you want to add as a member to thelist. (required) > > Usage notes: > The :list_slug portion of the request path should be the slug of thelistyou > want to add a member to. > > Supported formats: > xml, json > > e.g. > curl -u USERNAME:PASSWORD -d > "id=123456789"http://http://twitter.com/noradio/tall-people/members.xml > > GET '/:user/:list_slug/members.:format' > Members of the specifiedlist. > > Supported formats: > xml, json > > e.g. > curl -u USERNAME:PASSWORDhttp://twitter.com/noradio/tall-people/members.xml > > DELETE '/:user/:list_slug/members.:format' > Remove a member from the specifiedlist. > > Parameters: > * id: the id of the user you want to remove as a member from thelist. > (required) > > Usage notes: > The :list_id portion of the request path should be the slug of thelistyou > want to add a member to. > > Supported formats: > xml, json > > e.g. > curl -u USERNAME:PASSWORD -X DELETE -d > "id=123456789"http://twitter.com/nor
[twitter-dev] When will List API release?
Hi all, this is my first post :D I am a Twitter Client Developer , Do anyone know when the twitter list API will be released?? or the API is already released?? Thanks :)
