A problem with rate limits


#1

This concerns the REST API. I’m posting here in the hope that it is still on-topic. If I should post somewhere else, please let me know.

+++

Hi!

The following works from my terminal (I’ve removed the client
secret)…

curl -i ‘https://api.github.com/users/jecs-imperial?client_id=de17bf767
c5385f02f91&client_secret=xxxx’

…with the rate limits increased:

HTTP/1.1 200 OK
Server: GitHub.com
Date: Sun, 29 Jul 2018 18:29:06 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 1364
Status: 200 OK
X-RateLimit-Limit: 5000
X-RateLimit-Remaining: 4997
X-RateLimit-Reset: 1532892427

However, when I try a genuine API query, the rate limit remains low…

curl -i ‘https://api.github.com/repos/jecs-imperial/induction/issues?st
ate=all&clientId=de17bf767c5385f02f91&clientSecret=xxxx’

HTTP/1.1 200 OK
Server: GitHub.com
Date: Sun, 29 Jul 2018 19:00:57 GMT
Content-Type: application/json; charset=utf-8
Content-Length: 5
Status: 200 OK
X-RateLimit-Limit: 60
X-RateLimit-Remaining: 42
X-RateLimit-Reset: 1532892427
Cache-Control: public, max-age=60, s-maxage=60
Vary: Accept
ETag: “98f0c1b396a4e5d54f4d5fe561d54b44”
X-GitHub-Media-Type: github.v3; format=json
Access-Control-Expose-Headers: ETag, Link, Retry-After, X-GitHub-OTP,
X-RateLimit-Limit, X-RateLimit-Remaining, X-RateLimit-Reset, X-OAuth-
Scopes, X-Accepted-OAuth-Scopes, X-Poll-Interval
Access-Control-Allow-Origin: *
Strict-Transport-Security: max-age=31536000; includeSubdomains; preload
X-Frame-Options: deny
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Referrer-Policy: origin-when-cross-origin, strict-origin-when-cross-
origin
Content-Security-Policy: default-src ‘none’
X-Runtime-rack: 0.023266
X-GitHub-Request-Id: ADF2:241E:21FAD69:505C238:5B5E0EE9

[

]

I get the same result whether I try this from the command line (as
here) or from within the application itself.

Can you please explain to me what exactly is going wrong? Thanks!

Kind regards,

James


#2

This is fixed. It was a mistake with the query parameter names, that is ‘clientId’ instead of ‘client_id’, etc.