You're actually looking at the HTTP headers for the server you're accessing
on your computer.

This kind of information is available on the level of your application
that's actually making a request to Twitter and processing the data. Your
library is likely abstracting this away for you. You should be able to find
some methods in the library to either reach the response headers directly,
or an abstraction around the headers and/or rate limiting specifically.

I'm not familiar with that specific library, but eventually you'll have a
core HTTP object of some kind that's actually making the requests -- that
objectspace will contain methods to examine the headers directly.

@episod <http://twitter.com/episod> - Taylor Singletary - Twitter Developer
Advocate


On Tue, Mar 8, 2011 at 10:41 AM, m36tb6ll <raeste...@gmail.com> wrote:

>
> Thanks for the reply, Taylor...
>
> I'm quite new at this so I'll try to explain the best I could. I am
> using Sachin Khosla's Twitter OAuth library and am using GET users/
> lookup. After the page already have loaded, I checked the headers and
> this is what I am seeing using Firebug:
>
> Response Headers
>
> Date    Tue, 08 Mar 2011 18:38:52 GMT
> Content-Type    text/html
> Connection      close
> Server  Apache/2
> X-Powered-By    PHP/5.2.17
> Expires Thu, 19 Nov 1981 08:52:00 GMT
> Cache-Control   no-store, no-cache, must-revalidate, post-check=0, pre-
> check=0
> Pragma  no-cache
> Content-Length  6013
>
> Request Headers
>
> Host    bslplus.m36tb6ll.com
> User-Agent      Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:
> 1.9.2.14) Gecko/20110218 Firefox/3.6.14
> Accept  */*
> 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
> Referer
>
> http://bslplus.m36tb6ll.com/scripts/indexCallback.php?oauth_token=IkZnC9Cq7MvlRpPnKjM8Lx8uQLuuOxz7aIO7pI0GeI&oauth_verifier=fL5q1rapYVOCXDUxTli1JRI8YS8FYyXpXSKpXayu2v0
> Cookie  PHPSESSID=3839f152da9eae907ff976f88dd45030;
> __utma=45007288.931001284.1299609306.1299609306.1299609306.1;
> __utmb=45007288.1.10.1299609306; __utmc=45007288;
> __utmz=45007288.1299609306.1.1.utmcsr=(direct)|utmccn=(direct)|
> utmcmd=(none)
>
>
> Thanks in advance..
>
>
> On Mar 9, 12:37 am, Taylor Singletary <taylorsinglet...@twitter.com>
> wrote:
> > Can you provide an example execution where they are missing?
> >
> > The twurl console app has a trace mode that also provides the headers of
> the
> > response.https://github.com/marcel/twurl
> >
> > If you run a command like:
> >
> > twurl --trace /1/statuses/home_timeline.json?count=1 | grep x-ratelimit
> >
> > It will yield headers like these under normal operation:
> > x-ratelimit-reset: 1299604011
> > x-ratelimit-limit: 350
> > x-ratelimit-class: api_identified
> > x-ratelimit-remaining: 338
> >
> > Taylor
> >
> > @episod <http://twitter.com/episod> - Taylor Singletary - Twitter
> Developer
> > Advocate
> >
> > On Tue, Mar 8, 2011 at 7:25 AM, m36tb6ll <raeste...@gmail.com> wrote:
> >
> > > Hi -- I can't seem to see the X-Ratelimits in the headers after an
> > > authenticated call. Was it removed?
> >
> > > Thanks--
> >
> > > --
> > > 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
>
> --
> 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
>

-- 
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

Reply via email to