3 ms·
I realize that, at best, this is only tangentially related to security, but nginx's logging is quite frustrating. It'll log something that's completely out of y
by latch 6y ago
I realize that, at best, this is only tangentially related to security, but nginx's logging is quite frustrating. It'll log something that's completely out of your control (like invalid SSL requests) as a [crit]
You end up having patterns in your log ingestion to drop errors. Or, and this is the security concern, you start to ignore nginx errors.
- cpach 6y agoYeah that’s a weird design choice for an application that is usually configured to allow requests from just about anyone on the Internet.
- avian 6y agoThis reminds me of a similar issue in Apache: it will log 500 “internal server error” when (if I recall correctly) clients close connection before SSL handshake is complete. Quite frustrating to try to figure out where your application is crashing only to find out there’s no bug and it’s only someone running a port scan or something.