3 ms·

I would say it's disingenuous to claim sending HTTP status and body that is not expected for a period of time is not blocking them for that period of time. You

I would say it's disingenuous to claim sending HTTP status and body that is not expected for a period of time is not blocking them for that period of time. You can be pedantic and claim "but they can still access the server" but in reality that client is blocked for a period of time.

kstrauser 2y ago
In that case, I should be irate that the AWS API blocks me many times per day. Run `aws cli service some-paginated-thing` and see how many retries you get during normal, routine operation. But I’m not, because they’re not blocking me. They’re asking my client to slow down. Neither AWS nor Rachel’s blog owes me unlimited requests per unit time, and neither have “blocked” me when I violate they policies.
- that_guy_iain 2y ago
  They literally do block you for a period of time until you are out of the rate limit. That is how rate limits work. That's why you don't get to access the resource you requested, because their system literally blocked you from doing so. See when you're trying to be pedantic and all about semantics, you should make sure you've crossed your Ts and dotted your Is. > Block – AWS WAF blocks the request and applies any custom blocking behavior that you've defined. from https://docs.aws.amazon.com/waf/latest/developerguide/waf-rule-statement-type-rate-based-request-limiting.html https://docs.aws.amazon.com/waf/latest/developerguide/waf-ru... And my favourite > Rate limiting blocks users, bots, or applications that are over-using or abusing a web property. Rate limiting can stop certain kinds of bot attacks. From CloudFlare's explainer https://www.cloudflare.com/learning/bots/what-is-rate-limiting/ https://www.cloudflare.com/learning/bots/what-is-rate-limiti... Every documentation on rate limit will include the word block. Because that's what you do, you allow access for a specific amount of requests and then block those that go over.

kstrauser 2y ago

In that case, I should be irate that the AWS API blocks me many times per day. Run `aws cli service some-paginated-thing` and see how many retries you get during normal, routine operation. But I’m not, because they’re not blocking me. They’re asking my client to slow down. Neither AWS nor Rachel’s blog owes me unlimited requests per unit time, and neither have “blocked” me when I violate they policies.

that_guy_iain 2y ago
They literally do block you for a period of time until you are out of the rate limit. That is how rate limits work. That's why you don't get to access the resource you requested, because their system literally blocked you from doing so. See when you're trying to be pedantic and all about semantics, you should make sure you've crossed your Ts and dotted your Is. > Block – AWS WAF blocks the request and applies any custom blocking behavior that you've defined. from https://docs.aws.amazon.com/waf/latest/developerguide/waf-rule-statement-type-rate-based-request-limiting.html https://docs.aws.amazon.com/waf/latest/developerguide/waf-ru... And my favourite > Rate limiting blocks users, bots, or applications that are over-using or abusing a web property. Rate limiting can stop certain kinds of bot attacks. From CloudFlare's explainer https://www.cloudflare.com/learning/bots/what-is-rate-limiting/ https://www.cloudflare.com/learning/bots/what-is-rate-limiti... Every documentation on rate limit will include the word block. Because that's what you do, you allow access for a specific amount of requests and then block those that go over.