202 responses count toward API rate limit

jasonrudolph · jasonrudolph · commit 06a5a6cfd227 · 2013-05-15T15:27:41.000-04:00
If 202 responses did *not* count toward the rate limit, then a single
API user could queue up jobs for every single repository. That would
cause all other API users to wait longer for *their* statistics jobs to
complete. That's not cool. Share the road.
diff --git a/content/v3/repos/statistics.md b/content/v3/repos/statistics.md
@@ -15,13 +15,13 @@ types of repository activity.
 Computing repository statistics is an expensive operation, so we try to return cached
 data whenever possible.  If the data hasn't been cached when you query a repository's
 statistics, you'll receive a `202` response; a background job is also fired to
-start compiling these statistics.  Subsequent requests should return the data.
+start compiling these statistics. Give the job a few moments to complete, and
+then submit the request again. If the job has completed, that request will receive a
+`200` response with the statistics in the response body.
 
 Repository statistics are cached by the SHA of the repository's default branch,
 which is usually master; pushing to the default branch resets the statistics cache.
 
-**NOTE:** `202` responses do *not* count towards API rate limits.
-
 ## Get contributors list with additions, deletions, and commit counts
 
     GET /repos/:owner/:repo/stats/contributors
