# Rate limiting ## What is it? Rate limiting prevents us from sending large numbers of requests to a target. It can also be referred to as throttling. A simple example: * An application has a login form * When a request is made to login, the IP is saved and a counter assigned * If more than 10 attempts are made within 1minute the IP is blocked ## Checklist * [ ] Can we identify how the rate-limiting is being applied? * [ ] Can we spoof the a header that's being used * [ ] `X-Real-IP` * [ ] `X-Forwarded-For` * [ ] `X-Originating-IP` * [ ] `Client-IP` * [ ] `True-Client-IP` * [ ] Can we use other user agents? * [ ] Can we use different cookies or session tokens? * [ ] Can we tamper with HTTP verbs * [ ] Can we decrease the frequency of requests and leave overnight? * [ ] Can we create legitimate-looking behaviour --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://appsecexplained.gitbook.io/appsecexplained/bypassing-controls/rate-limiting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.