Page MenuHomeSoftware Heritage

gitlab-lister: Investigate rate limit implementation further
Open, NormalPublic


It's been implemented and so far potentially used for the main instance.
It's based on their response's headers [1]:

RateLimit-Limit: 600
RateLimit-Observed: 1
RateLimit-Remaining: 599
RateLimit-Reset: 1561888426
RateLimit-ResetTime: Sun, 30 Jun 2019 09:53:46 GMT

Check other instances (salsa's debian for example) for a similar use pattern. [1]

[1] Checking a head query on salsa does not render those:

curl -I                                                                                                                                                                                                                                                                                                                    ~
HTTP/1.1 200 OK
Date: Sun, 30 Jun 2019 09:52:11 GMT
Server: Apache
Referrer-Policy: no-referrer
X-Xss-Protection: 1
Strict-Transport-Security: max-age=15552000
Public-Key-Pins: pin-sha256="JX3rnmIs7tgG+zN5HNBXaA8rfi6RKVlvOPGnn+uJ/xI="; pin-sha256="5xBLLloCLM71PnTWnZuxgQmaW3ziZhvPuSBbwKI3D3o="; max-age=5184000
Cache-Control: no-cache
Content-Length: 18197
Content-Type: application/json
Link: <>; rel="next", <>; rel="first", <>; rel="last"
Vary: Origin
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-Next-Page: 2
X-Page: 1
X-Per-Page: 20
X-Request-Id: xKLWNvr19L5
X-Runtime: 0.505211
X-Total: 31818
X-Total-Pages: 1591
X-Clacks-Overhead: GNU Terry Pratchett


Event Timeline

ardumont triaged this task as Normal priority.Jun 30 2019, 11:55 AM
ardumont created this task.

I did not find anything specific to rate limit policy for salsa.
I found an api usage best practices chapter though [1].


ardumont updated the task description. (Show Details)Jul 1 2019, 10:04 AM