3 ms·
It depends on how it's pitched. :) If you went with something like "using caching to avoid hitting API limits" it sounds legit. Whereas if you went with somet
by justinclift 3y ago
It depends on how it's pitched. :)
If you went with something like "using caching to avoid hitting API limits" it sounds legit.
Whereas if you went with something like "getting around Company Foo's API rate limits" it sounds like you're exploiting a bug in their system.
If you did present the system as spoofing requests to subvert a rate limit / blacklist, as per:
#4, my presentation was about how I reverse engineered the Robinhood API, spoofed
requests to get around their “security”, and used two levels of caching (Redis and a
typical relational DB) to subvert rate limiting/IP blacklisting
... then that doesn't sound like the legit use case scenario. ;)
Your further follow up discussion makes it sound like you were just using a self-developed caching system though, and presented it terribly for the target audience.
- gymbeaux 3y agoI don't know that there's a way you can pitch your reasoning to me where I would agree. The two statements sound equivalent to me. API rate limits are just that- rate limits. This is not akin to hacking and a software engineer I doubt would ever confuse it with hacking of any kind. What would be an example of "exploiting a rate limiting bug"? Either the server limits/throttles requests, or it doesn't.
- justinclift 3y ago> What would be an example of "exploiting a rate limiting bug"? All sorts of possibilities spring to mind for that. :) Here's a hypothetical example. Lets say you discovered a logic bug in the API limit code along these lines: "So, it turns out if you have an `X-Forwarded-For` header in the request, then the request is processed properly except it isn't counted towards the limit. Effectively a bypass." Exploiting this one would of course be trivial, as you'd just need to set that header for all your requests.