Header changed for x-rate-limit-remaining (cap Vs non cap letters)



It seems that headers have changed, people that are looking exactly for “X-Rate-Limit-Remaining” (like written in documentation https://dev.twitter.com/docs/rate-limiting/1.1) will fail as it is now returning “x-rate-limit-remaining”.

This change made all our rate limit checks failed, and loose many data.

I’ve got some other questions on that:

Was this a planned change?
If yes, how can I suscribe to get these changes in the future?
Is this planned to change again?

Thank you,


Was this happening to you on all methods or just a subset?

Sorry if it caused you an inconvenience – HTTP headers are typically to be interpreted as case-insensitive according to the RFC 2616: http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2


Hi Taylor,

Thank you for the quick reply, now we know and we’ve just patch our code.

I’m not pretty sure, but this happened at least on followers/ids and users/show

Kind regards,