Make Rate Limiter Aggressive on statuses > 400
This is based on the hypothesis that the Node
application shouldn't be getting hit with a large number of requests in
general thanks to Fastly and certainly shouldn't be getting hit with a
large number of requests that have status codes greater than 400 unless
a user or bot is trying to guess random URLs and as a result. For
example, see this IP address that caused some site issues on October 3
Co-authored-by: Chiedo <chiedo@users.noreply.github.com>
Co-authored-by: Jason Etcovitch <jasonetco@github.com>
* minor clarification in comment
* handle scenario where a new version has been injected into an old path
* update oldEnterprisePath regex and comment
* lint
* Create schema-event-2.js
* Update schema-event-2.js
* Expand a few field names
* Avoid id and timestamp from the FAQ
* Update schema-event-2.js
* Update from meeting with Kath and Jason
* Update schema-event-2.js
* Update schema-event-2.js
* Update schema-event-2.js
* Add more information to the codescan enabling topic - WiP
* Add more details and s/shots to the Enabling topic
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Make change suggested by Justin, but in step 5 rather than step 4.
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Not all workflows will have `on:push` and `on:pull_request` so clarify that this refers to the CodeQL workflow.
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Update content/github/finding-security-vulnerabilities-and-errors-in-your-code/enabling-code-scanning-for-a-repository.md
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
* Revert changes to this file to the file as it currently is on main
* Attempt to remove package.json
Co-authored-by: Shati Patel <42641846+shati-patel@users.noreply.github.com>
Co-authored-by: Chiedo <chiedo@users.noreply.github.com>
Co-authored-by: Sarah Schneider <sarahs@users.noreply.github.com>
