* remove outdated and redundant context.enterpriseVersions and add new context.enterpriseServerVersions
* update references from context.enterpriseVersions -> context.enterpriseServerReleases
* add test
* also test oldest supported enterprise version in addition to the latest
* Script to update not-free-pro-team conditionals (#16060)
* script to update not-free-pro-team conditionals
* change string to regex so we can do replace all
* remove stray test.only
* Update middleware/context.js
Co-authored-by: James M. Greene <JamesMGreene@github.com>
* Update tests/unit/page.js
Co-authored-by: James M. Greene <JamesMGreene@github.com>
* Update tests/unit/page.js
Co-authored-by: James M. Greene <JamesMGreene@github.com>
* Update tests/fixtures/page-versioned-for-all-enterprise-releases.md
Co-authored-by: James M. Greene <JamesMGreene@github.com>
Co-authored-by: James M. Greene <JamesMGreene@github.com>
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>
* remove FEATURE_NEW_VERSIONS from feature-flags.json
* remove process.env.FEATURE_NEW_VERSIONS from include files
* remove process.env.FEATURE_NEW_VERSIONS from lib files
* remove process.env.FEATURE_NEW_VERSIONS from middleware files
* remove process.env.FEATURE_NEW_VERSIONS from script files
* remove process.env.FEATURE_NEW_VERSIONS from test files
* update test fixtures to use new versions as canonical fixtures
