Thus spake Chris Caputo (ccap...@alt.net) on Tue, Aug 09, 2022 at 07:11:02PM
+:
> Dale, if you are getting 200 for an obviously bad api-key, then the
> authentication format is not correct. Examples/details at:
>
> https://github.com/peeringdb/peeringdb/issues/1220#issuecomment-1209763911
Dale, if you are getting 200 for an obviously bad api-key, then the
authentication format is not correct. Examples/details at:
https://github.com/peeringdb/peeringdb/issues/1220#issuecomment-1209763911
With a correctly formated auth request, 401 (unauth) will be returned for
a bad key.
> However, for a read-only API key, how does one know if it's working?
> I set 'Authorization': 'Api-Key foo-bar-1234-4312' for a GET, and I
> got results back vs a 4xx error code. So from an error handling
> perspective it seems hard to gauge if I am using a valid api key
> getting premium
Thus spake Chris Caputo (ccap...@alt.net) on Mon, Aug 08, 2022 at 04:41:17PM
+:
> Per the below plan, this change was just implemented:
>
> ---
> On August 8th, adjust and watch for feedback from the community:
>
> - anonymous queries limited to 20/minute per IP address
> -
Per the below plan, this change was just implemented:
---
On August 8th, adjust and watch for feedback from the community:
- anonymous queries limited to 20/minute per IP address
- authenticated queries limited to 60/minute per user/org
---
Please advise if you run into any issues.
Thank
