nginx.git/src/http/modules/ngx_http_log_module.c, branch release-1.30.0 nginx Access log: support for disabling escaping (ticket #1450). 2018-03-01T08:42:55+00:00 Vladimir Homutov vl@nginx.com 2018-03-01T08:42:55+00:00 764737256521de5c34f7ce1cc1b27bf440b6cced Based on patches by Johannes Baiter <johannes.baiter@bsb-muenchen.de> and Calin Don. 
Based on patches by Johannes Baiter <johannes.baiter@bsb-muenchen.de>
and Calin Don.
Fixed ngx_open_cached_file() error handling. 2017-03-28T11:21:38+00:00 Sergey Kandaurov pluknet@nginx.com 2017-03-28T11:21:38+00:00 9ad18e43ac2c9956399018cbb998337943988333 If of.err is 0, it means that there was a memory allocation error and no further logging and/or processing is needed. The of.failed string can be only accessed if of.err is not 0. 
If of.err is 0, it means that there was a memory allocation error
and no further logging and/or processing is needed.  The of.failed
string can be only accessed if of.err is not 0.
Access log: removed dead ev->timedout check in flush timer handler. 2017-03-07T15:51:12+00:00 Maxim Dounin mdounin@mdounin.ru 2017-03-07T15:51:12+00:00 c1d8318d3112a2752971d76fc15d1fca8557691d The ev->timedout flag is set on first timer expiration, and never reset after it. Due to this the code to stop the timer when the timer was canceled never worked (except in a very specific time frame immediately after start), and the timer was always armed again. This essentially resulted in a buffer flush at the end of an event loop iteration. This behaviour actually seems to be better than just stopping the flush timer for the whole shutdown, so it is preserved as is instead of fixing the code to actually remove the timer. It will be further improved by upcoming changes to preserve cancelable timers if there are other timers blocking shutdown. 
The ev->timedout flag is set on first timer expiration, and never reset
after it.  Due to this the code to stop the timer when the timer was
canceled never worked (except in a very specific time frame immediately
after start), and the timer was always armed again.  This essentially
resulted in a buffer flush at the end of an event loop iteration.

This behaviour actually seems to be better than just stopping the flush
timer for the whole shutdown, so it is preserved as is instead of fixing
the code to actually remove the timer.  It will be further improved by
upcoming changes to preserve cancelable timers if there are other timers
blocking shutdown.
Access log: support for json escaping. 2016-12-15T13:25:42+00:00 Valentin Bartenev vbart@nginx.com 2016-12-15T13:25:42+00:00 c40d8ddc5d907ebd90f85cf362f501d2cf3e05a2 






Avoid left-shifting integers into the sign bit, which is undefined.
2016-07-07T18:02:28+00:00

Sergey Kandaurov
pluknet@nginx.com

2016-07-07T18:02:28+00:00

6299f5e9149483251bbbcc8ad26cf29b6109e75c

Found with UndefinedBehaviorSanitizer.





Found with UndefinedBehaviorSanitizer.







Access log: restricted "log_format" to "http" level.
2014-12-01T11:51:36+00:00

Sergey Kandaurov
pluknet@nginx.com

2014-12-01T11:51:36+00:00

778cc4b42ea85e19a8ebf6c1a42fc636e48ec309

Specifying the "log_format" directive on levels other than "http"
is deprecated since 73d37e1ccb91 (1.1.11).





Specifying the "log_format" directive on levels other than "http"
is deprecated since 73d37e1ccb91 (1.1.11).







Access log: cancel the flush timer on graceful shutdown.
2014-08-25T09:41:31+00:00

Valentin Bartenev
vbart@nginx.com

2014-08-25T09:41:31+00:00

f9b99baed366b855cef24f3443be6337583ac0f3

Previously, it could prevent a worker process from exiting
for up to the configured flush timeout.





Previously, it could prevent a worker process from exiting
for up to the configured flush timeout.







Access log: fixed the "if=" parameter with buffering (ticket #625).
2014-09-13T17:47:13+00:00

Valentin Bartenev
vbart@nginx.com

2014-09-13T17:47:13+00:00

152d92b4b76303d7b2d64e76cadf6d466df48f7f

It might not work if there were more than one "access_log" directives
pointed to the same file and duplicate buffer parameters.





It might not work if there were more than one "access_log" directives
pointed to the same file and duplicate buffer parameters.







Access log: allowed logs to syslog with "if=" (ticket #596).
2014-08-05T20:22:36+00:00

Maxim Dounin
mdounin@mdounin.ru

2014-08-05T20:22:36+00:00

8f0f4c10e91a82e6f636d792c14cc608c06ca37d












Access log: fix default value, broken by cb308813b453.
2014-06-03T17:53:48+00:00

Piotr Sikora
piotr@cloudflare.com

2014-06-03T17:53:48+00:00

a1a8defb4956ce5416ff633c47da2dc4d473fac0

log->filter ("if" parameter) was uninitialized when the default value
was being used, which would lead to a crash (SIGSEGV) when access_log
directive wasn't specified in the configuration.

Zero-fill the whole structure instead of zeroing fields one-by-one
in order to prevent similar issues in the future.

Signed-off-by: Piotr Sikora <piotr@cloudflare.com>





log->filter ("if" parameter) was uninitialized when the default value
was being used, which would lead to a crash (SIGSEGV) when access_log
directive wasn't specified in the configuration.

Zero-fill the whole structure instead of zeroing fields one-by-one
in order to prevent similar issues in the future.

Signed-off-by: Piotr Sikora <piotr@cloudflare.com>