As I'm about to launch some major additions to my site (and launch another
site) I've been starting to get my act together in regards to development,
e.g. finally starting to use git, getting ready for a responsive redesign,
etc.
I've realized that it would probably be wise to develop locally by r
So, I've found out more about my situation. Apparently, limit_conn_zone
stuff I'm doing on Nginx applies to HAProxy only which is in front of my
Nginx.
I guess I have two options:
1. Use HAProxy (instead of Nginx) for request/connection limiting.
2. Limit requests/connections on Nginx based on X
Hello!
On Sun, Apr 14, 2013 at 6:22 AM, gadh wrote:
> I'm trying to hold a client request to backend (not go to the server yet),
> issue an upstream request to another server, then parse the upstream
> response, store it in my orig. request ctx, only then go to backend server
> (original request),
The issue has been resolved. It was monit who was creating issues and
closing nginx connection during buffering. I changed the version of monit
from 4.1* to 5.1* and there ain't no error in logs regarding "signal
process started" . Thanks
On Sat, Apr 13, 2013 at 7:24 PM, shahzaib shahzaib wrote:
I'm trying to hold a client request to backend (not go to the server yet),
issue an upstream request to another server, then parse the upstream
response, store it in my orig. request ctx, only then go to backend server
(original request), and in the output filter inject some of the ctx data i
store
