We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I know this is an common problem with NGINX (https://www.miklix.com/nginx/deleting-nginx-cache-puts-critical-unlink-errors-in-error-log/) but is it possible to sync with NGINX internals after PURGE so this "critical" error won't be logged?
PURGE
The text was updated successfully, but these errors were encountered:
@denji Are you looking at completing this enhancement some time this year? Would be really nice to sync NGINX's internal keystone with the PURGE.
Sorry, something went wrong.
No branches or pull requests
I know this is an common problem with NGINX (https://www.miklix.com/nginx/deleting-nginx-cache-puts-critical-unlink-errors-in-error-log/) but is it possible to sync with NGINX internals after
PURGE
so this "critical" error won't be logged?The text was updated successfully, but these errors were encountered: