Thank you. Normally I don’t even use the info logs but while troubleshooting a memory problem, I was looking through them and noticed that even just using an error_log file at the info level was writing a ton of data despite that config. I guess I can just shut the info log back off.
— Lance Dockins > On Wednesday, Sep 20, 2023 at 1:41 PM, Maxim Dounin <mdou...@mdounin.ru > (mailto:mdou...@mdounin.ru)> wrote: > Hello! > > On Wed, Sep 20, 2023 at 11:47:48AM -0500, Lance Dockins wrote: > > > Is there a reason that Nginx continuously logs the sort of message below in > > the info log when client_body_in_file_only is set to either "clean" or > > "on"? Regardless of which of those two settings you're using for that > > directive, the request body is always going to be buffered to a temporary > > file (that is the whole point of that setting). > > > > "[notice] 3951130#3951130: *769735 a client request body is buffered to a > > temporary file" > > > > Seems like even the info log should be suppressing that notice if you're > > using settings that force the request body to a temp file. > > That's exactly the reason why it is logged at the "notice" level, > and not "warn" as it used to be under normal conditions. If you > don't want to see these messages, consider configuring error_log > logging level to a higher one, see http://nginx.org/r/error_log > for details. > > -- > Maxim Dounin > http://mdounin.ru/ > _______________________________________________ > nginx mailing list > nginx@nginx.org > https://mailman.nginx.org/mailman/listinfo/nginx
_______________________________________________ nginx mailing list nginx@nginx.org https://mailman.nginx.org/mailman/listinfo/nginx
