-
-
Notifications
You must be signed in to change notification settings - Fork 218
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERR_ERL_CREATED_IN_REQUEST_HANDLER #452
Comments
…T_HANDLER validation check. Relates to #452
Hum, that's confusing. Can you post the full stack trace it logs with the error? The way the check works is that it looks for the string "Layer.handle [as handle_request]" in the stack trace. Perhaps that string is appearing for some reason? I'm not sure why it would be intermittent, though.. Also, as a workaround, you can disable that validation check: const publicAPIlimiter = rateLimit({
windowMs: <someValue>,
limit: <several allowed>,
validate: {
creationStack: false
}
});
const authRateLimit = rateLimit({
windowMs: <someSmallerValue>,
limit: <SmallerLimit>,
validate: {
creationStack: false
}
}); |
Here is the stack. Thank you for your attention.
|
What's at and around line 36 in your Also, I'm a little perplexed as to how passport's authenticate function is the last item in the stack trace - is it getting called in a |
Just checking back in, did you make any progress on this? If not, could you share the snippet of your |
Sorry was sick - catching up. |
Description
Getting this error - in what appears to be an inaccurate circumstance - not sure how to replicate, it is intermittent.
Our intent is to limit 2 of our URL paths that publicly exposed to have limited use frequency.
This follows the Usage outline in the documentation: https://express-rate-limit.mintlify.app/quickstart/usage
Notably the creation (class is created as part of the app.ts startup) is done before assignment to the express middleware.
Not sure why we sometimes get the error mentioned in the title - ideas?
TIA
Et
Library version
7.2.0
Node version
18.19.0
Typescript version (if you are using it)
5.3.3
Module system
ESM
The text was updated successfully, but these errors were encountered: