Yichun Zhang
Yichun Zhang
@junos Your example is not self-contained nor minimal so I cannot really run your case directly on our side and try to reproduce the problem. My hunch is that your...
@junos BTW, you can (temporarily) enable the nginx debugging logs in your OpenResty to confirm the internal redirects or other important details of your request. If you are using the...
@junos You should check if your nginx workers ever crashed. Crashes must always be fixed.
Please rebase to the latest git master. Thank you :)
@dolik-rce Just the lack of time and higher priority items. I think @thibaultcha will take care of this :)
@rohitjoshi Will you use Valgrind to run your nginx process? You'd better turn off `daemon` and `master_process` in your `nginx.conf`. Also, it's better to specify the `./configure` options ``` --with-luajit-xcflags='-DLUAJIT_USE_VALGRIND...
@rohitjoshi Yeah, Valgrind is shaky on Mac OS X. Try running Valgrind against exactly the same OpenResty app and setup on Linux to see if you can find anything.
@rohitjoshi Still it's worth trying Valgrind since it can find memory issues that do not lead to segmentation faults. Ensure you have rebuilt OpenResty with the special `./configure` options I...
@rohitjoshi BTW, those options only work with valgrind runs though. Do not attempt to run the resulting nginx without valgrind.
@georgebashi Yes, this should be useful for its own right. But I'm curious about the reasons that you do not use the standard ngx_limit_req and ngx_limit_conn modules for your use...