This pull request ensures that both HTTP 403s responses with x-ratelimit-remaining: 0, as well as HTTP 429s are handled for rate limiting.
This deviates from Github's existing documentation, which states that HTTP 403s will be used with x-ratelimit-* headers. However, recent rate-limit blog posts from Github mention that HTTP 429 will be used.
Speaking with Github, they have advised that both should be handled.
Overview
This pull request ensures that both HTTP 403s responses with
x-ratelimit-remaining: 0
, as well as HTTP 429s are handled for rate limiting.This deviates from Github's existing documentation, which states that HTTP 403s will be used with
x-ratelimit-*
headers. However, recent rate-limit blog posts from Github mention that HTTP 429 will be used.Speaking with Github, they have advised that both should be handled.