Hi Thanks for your reply. I tried this but didn't have any luck with it. Based on the error reported on the error log (client closed permaturely connection while reading client request line), I'm wondering if i can instead ignore logging those errors in the access logs. Would you if that's possible? Thanks!! Cheers -- Imranby imran - Nginx Mailing List - English
Also to add on a bit more about the chrome connection issue which is causing the 400, I turned on info logging for error logs and when I get the 400, it logs a 'client closed prematurely connection while reading client request...' in the error logs. Cheers -- Imranby imran - Nginx Mailing List - English
Hello I'd like to know if its possible for me to log HTTP 400 errors to a different log file. Right now they go in the access log. To give some background, we've got this problem where if a single resource is requested from chrome, after the resource request is served, a http 400 error is logged in the access logs. This I've understood to be is due to the nature of connections opened by Chrby imran - Nginx Mailing List - English