Oops, sorry about that; I thought you meant to simply add "debug" to the log directive in the .conf. But! I updated to 0.8.31 and rebuilt with --with-debug (as per your recommendation) and everything works perfectly. Here's my final nginx.conf if anyone else will want to do something similar in the future. location /eve/ { proxy_pass http://127.0.0.1:9001;by davvv - Nginx Mailing List - English
Thanks for the advice Piotr, but instead of helping me, it just complicated the situation a whole lot more :P 2010/01/05 01:22:28 4020#0: signal 17 (SIGCHLD) received 2010/01/05 01:22:28 4020#0: worker process 4024 exited on signal 11 2010/01/05 01:22:28 4020#0: start worker process 9274 2010/01/05 01:22:28 4020#0: signal 29 (SIGIO) received 2010/01/05 01:22:29 4020#0: signal 17 (SIGCHby davvv - Nginx Mailing List - English
.eve is not technically an extension, it's just a resource flag I allocated in my C++ server (I plan to expand it later on). But either way, I'm pretty sure that part isn't the issue. It's just that I'm not sure how to redirect the FULL request as if it were fresh from the client AFTER an error has been served by my server (or proxy, or whatever you want to call it).by davvv - Nginx Mailing List - English
Yes, callback.eve is the correct resourceby davvv - Nginx Mailing List - English
I wrote a very scalable HTTP event server in C++ and I would like to make it work with nginx. My server is on port 9001, PHP-FPM is running on port 9000. My server is set up to return a 504 error when an event is found, and the 504 error should trigger the PHP backend. I've been trying to figure out a way to make it work with nginx and it's something so elementary, I think I'm just being realby davvv - Nginx Mailing List - English