<html xmlns="http://www.w3.org/1999/xhtml"><head> <title></title> <meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no"> </head> <body style="font-family:Helvetica;color:#000000;font-size:13px;"><img id="E6458E380395062CFC9DFF84F7EB4F39" alt="" width="0px" src="https://receipts.canarymail.io/track/23BE42F21B750115E03660019DCF8935_E6458E380395062CFC9DFF84F7EB4F39.png" height="0px"><div id="CanaryBody"> <div> 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.</div> <div><br></div> </div> <div id="CanarySig"> <div> <div style="font-family:Helvetica;">—<br><div>Lance Dockins</div><br></div> <div><br></div> </div> </div> <div id="CanaryDropbox"> </div> <blockquote id="CanaryBlockquote"> <div> <div>On Wednesday, Sep 20, 2023 at 1:41 PM, Maxim Dounin <<a href="mailto:mdounin@mdounin.ru">mdounin@mdounin.ru</a>> wrote:<br></div> <div>Hello!<br><br>On Wed, Sep 20, 2023 at 11:47:48AM -0500, Lance Dockins wrote:<br><br><blockquote type="cite">Is there a reason that Nginx continuously logs the sort of message below in<br>the info log when client_body_in_file_only is set to either "clean" or<br>"on"? Regardless of which of those two settings you're using for that<br>directive, the request body is always going to be buffered to a temporary<br>file (that is the whole point of that setting).<br><br>"[notice] 3951130#3951130: *769735 a client request body is buffered to a<br>temporary file"<br><br>Seems like even the info log should be suppressing that notice if you're<br>using settings that force the request body to a temp file.<br></blockquote><br>That's exactly the reason why it is logged at the "notice" level, <br>and not "warn" as it used to be under normal conditions. If you <br>don't want to see these messages, consider configuring error_log <br>logging level to a higher one, see http://nginx.org/r/error_log <br>for details.<br><br>-- <br>Maxim Dounin<br>http://mdounin.ru/<br>_______________________________________________<br>nginx mailing list<br>nginx@nginx.org<br>https://mailman.nginx.org/mailman/listinfo/nginx<br></div> </div> </blockquote> </body></html>