Mmmm... If you set it to debug you would probably get something to pop
up sooner rather than later
My error log level is set to 'error' and I typically see some ocsp
cert timeouts and the occasional client exceeding my request (rate)
limit settings... Not a lot ends up in the nginx error log (
That clears it up. Most of what I see in the error log is stuff I have no idea
how to fix. I will Google some errors and see what is fixable. The deal is my
websites work for me and I get no complaints.
Reading questions on the interwebs, most people get error messages when they
use curl on th
> I'm not sure I understand the question, but how does this sound? I
> use a map to catch requests that I don't want. For instance I return
> a 444 if I receive a "wget".
No, I don’t mean status codes on the HTTP level. Status code 444 is
not an error per se that would be sent to the error log, it
I'm not sure I understand the question, but how does this sound? I use a map to
catch requests that I don't want. For instance I return a 444 if I receive a
"wget".
Original Message
From: c...@tunnel53.net
Sent: June 14, 2020 5:40 AM
To: nginx@nginx.org
Reply-to: nginx@ngi
Hi folks,
Is there any surefire way to force Nginx to log an error?
Perhaps some carefully crafted GET request or similar.
The reason I’m asking is that I’m doing a lab with Nginx’ error
log. Therefore I would like to find a way so that I can force Nginx to
log an error. E.g. if I specify "error
