Skip to content
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

Make cache.max argument mandatory to avoid memory leak #27

Open
alekseykulikov opened this issue Oct 10, 2016 · 1 comment
Open

Make cache.max argument mandatory to avoid memory leak #27

alekseykulikov opened this issue Oct 10, 2016 · 1 comment

Comments

@alekseykulikov
Copy link

Without cache.max it produces memory leak, and enabling this middleware without options is dangerous for production deployment.

@alekseykulikov alekseykulikov changed the title Make cache.max argument mandatory Make cache.max argument mandatory to avoid memory leak Oct 10, 2016
@terinjokes
Copy link
Contributor

I don't think I can fix this until 2.0.

@terinjokes terinjokes added this to the 2.0 - The Next Generation milestone Aug 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants