I think the best debugging process is to reproduce your problem in curl, then show the curl -v output (passwords elided, naturally). If curl works and your home-rolled client does not, then you can use tcpdump(1) or some other packet sniffer and work out the deltas between the working solution and the non-working solution.
In this case, do you have access to the firehose? Can you use an existing client library? There are dozens of clients for the Streaming API out there. -John Kalucki http://twitter.com/jkalucki Twitter, Inc. On Sat, Sep 11, 2010 at 12:36 AM, omri <omridek...@gmail.com> wrote: > I request this URL : > http://stream.twitter.com/1/statuses/firehose.json > > i get this message on my compiler : > WARNING 2010-09-11 07:31:30,447 urlfetch_stub.py:284] Stripped > prohibited headers from URLFetch request: ['Host'] > > i think something is wrong with my permission. > > I read this doc. > > This is the code i wrote in prder to use the streaming : > > status_url = "http://stream.twitter.com/1/statuses/firehose.json"; > request = urllib2.Request(status_url) > auth = base64.encodestring('(username):(password)')[:-1] > request.add_header('Authorization', "basic %s" % auth) > firehose = urllib2.urlopen(request) > for tweet in firehose: > print tweet > > firehose.close > > thanks again > > > > On 9 ספטמבר, 18:02, John Kalucki <j...@twitter.com> wrote: > > Which URL are you requesting? What is the text message returned? Does > this > > doc help?http://dev.twitter.com/pages/streaming_api_response_codes > > > > -John > > > > > > > > On Thu, Sep 9, 2010 at 7:45 AM, omri <omridek...@gmail.com> wrote: > > > so.. > > > succeded with the username and password but now i have : > > > HTTPError: HTTP Error 403: Forbidden > > > > > I need something special to have access to the streaming resources? > > > > > On 9 ספטמבר, 17:03, Taylor Singletary <taylorsinglet...@twitter.com> > > > wrote: > > > > Hi Omri, > > > > > > With basic auth, you don't use your consumer key or secret at all. > > > Consumer > > > > key and secret are used when authorizing through OAuth, and the > > > > implementation is a bit more detailed than putting them in a header. > > > > > > In your case, you want to use basic authorization, which should be > easier > > > > for your initial implementation. > > > > > > Here are some pointers in the right direction for using basic auth > with > > > > Python's urllib2: > http://docs.python.org/library/urllib2.html#examples > > > > > > Taylor > > > > > > On Thu, Sep 9, 2010 at 6:56 AM, omri <omridek...@gmail.com> wrote: > > > > > this is the message i get : > > > > > > > File "C:\Python26\lib\urllib2.py", line 516, in > > > > > http_error_default > > > > > raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) > > > > > HTTPError: HTTP Error 401: Unauthorized > > > > > > > i think i dont know which username and password to type in the > header > > > > > - 'Authorization' 'basic (username:password) > > > > > the twitter's username? > > > > > the twitter api oauth? > > > > > > > thanks > > > > > > > On 9 ספטמבר, 15:42, John Kalucki <j...@twitter.com> wrote: > > > > > > What text message does it return with the 401 error? > > > > > > > > You can still use basic auth with streaming. Does that work for > you? > > > You > > > > > > should use your screenname and password for basic auth. > > > > > > > > -John Kaluckihttp://twitter.com/jkalucki > > > > > > Twitter, Inc. > > > > > > > > On Thu, Sep 9, 2010 at 2:48 AM, omri <omridek...@gmail.com> > wrote: > > > > > > > hi, > > > > > > > now it returns the 401 error. > > > > > > > It seems like I don't know what is the username and password i > > > should > > > > > > > insert. > > > > > > > > > is this ths oauth token? > > > > > > > what is the title of this fields? > > > > > > > > > API key, Consumer key, Consumer secret? > > > > > > > > > thanks > > > > > > > > > On 7 ספטמבר, 17:16, John Kalucki <j...@twitter.com> wrote: > > > > > > > > The Streaming API will print a short text message along with > > > errors > > > > > that > > > > > > > is > > > > > > > > often a very explicit indication of the problem. I don't > think it > > > > > throws > > > > > > > 500 > > > > > > > > errors (see: > > > > >http://dev.twitter.com/pages/streaming_api_response_codes) > > > > > > > so > > > > > > > > something odd is going on. If anything, it is throwing a 406, > as > > > you > > > > > > > haven't > > > > > > > > provided parameters to track. > > > > > > > > > > -John Kaluckihttp://twitter.com/jkalucki > > > > > > > > Twitter, Inc. > > > > > > > > > > On Tue, Sep 7, 2010 at 4:38 AM, omri <omridek...@gmail.com> > > > wrote: > > > > > > > > > def run (self): > > > > > > > > > status_url = " > > >http://stream.twitter.com/1/statuses/filter.json"; > > > > > > > > > request = urllib2.Request(status_url) > > > > > > > > > print request > > > > > > > > > auth = base64.encodestring('Consumer key:Consumer > > > secret')[:-1] > > > > > > > > > request.add_header('Authorization', 'basic %s' % auth) > > > > > > > > > firehose = urllib2.urlopen(request) > > > > > > > > > for tweet in firehose: > > > > > > > > > print tweet > > > > > > > > > > > firehose.close > > > > > > > > > > > when printing the request i have 500 error, it is not > > > reachable. > > > > > > > > > > > do you have an idea why? > > > > > > > > > > > -- > > > > > > > > > Twitter developer documentation and resources: > > > > > > >http://dev.twitter.com/doc > > > > > > > > > API updates via Twitter:http://twitter.com/twitterapi > > > > > > > > > Issues/Enhancements Tracker: > > > > > > > > >http://code.google.com/p/twitter-api/issues/list > > > > > > > > > Change your membership to this group: > > > > > > > > > > http://groups.google.com/group/twitter-development-talk?hl=en > > > > > > > > > -- > > > > > > > Twitter developer documentation and resources: > > > > >http://dev.twitter.com/doc > > > > > > > API updates via Twitter:http://twitter.com/twitterapi > > > > > > > Issues/Enhancements Tracker: > > > > > > >http://code.google.com/p/twitter-api/issues/list > > > > > > > Change your membership to this group: > > > > > > >http://groups.google.com/group/twitter-development-talk?hl=en > > > > > > > -- > > > > > Twitter developer documentation and resources: > > >http://dev.twitter.com/doc > > > > > API updates via Twitter:http://twitter.com/twitterapi > > > > > Issues/Enhancements Tracker: > > > > >http://code.google.com/p/twitter-api/issues/list > > > > > Change your membership to this group: > > > > >http://groups.google.com/group/twitter-development-talk?hl=en > > > > > -- > > > Twitter developer documentation and resources: > http://dev.twitter.com/doc > > > API updates via Twitter:http://twitter.com/twitterapi > > > Issues/Enhancements Tracker: > > >http://code.google.com/p/twitter-api/issues/list > > > Change your membership to this group: > > >http://groups.google.com/group/twitter-development-talk?hl=en > > -- > Twitter developer documentation and resources: http://dev.twitter.com/doc > API updates via Twitter: http://twitter.com/twitterapi > Issues/Enhancements Tracker: > http://code.google.com/p/twitter-api/issues/list > Change your membership to this group: > http://groups.google.com/group/twitter-development-talk?hl=en > -- Twitter developer documentation and resources: http://dev.twitter.com/doc API updates via Twitter: http://twitter.com/twitterapi Issues/Enhancements Tracker: http://code.google.com/p/twitter-api/issues/list Change your membership to this group: http://groups.google.com/group/twitter-development-talk?hl=en
