wn the old ones.
>>> There's absolutely no downtime involved in this process.
>>>
>>>
>>> From: nginx on behalf of Ajay Garg <
>>> ajaygargn...@gmail.com>
>>> Reply-To: "nginx@nginx.org"
>>> Date: Sunday, 9
tart
>> new workers, and gracefully shut down the old ones.
>> There's absolutely no downtime involved in this process.
>>
>>
>> From: nginx on behalf of Ajay Garg <
>> ajaygargn...@gmail.com>
>> Reply-To: "nginx@nginx.org"
>>
s.
> There's absolutely no downtime involved in this process.
>
>
> From: nginx on behalf of Ajay Garg <
> ajaygargn...@gmail.com>
> Reply-To: "nginx@nginx.org"
> Date: Sunday, 9 April 2017 at 15.55
> To: "nginx@nginx.org"
> Subject: Mechanism
the configuration, start
>> new workers, and gracefully shut down the old ones.
>> There's absolutely no downtime involved in this process.
>>
>>
>> From: nginx on behalf of Ajay Garg <
>> ajaygargn...@gmail.com>
>> Reply-To: "nginx@ngi
ime involved in this process.
>
>
> From: nginx on behalf of Ajay Garg <
> ajaygargn...@gmail.com>
> Reply-To: "nginx@nginx.org"
> Date: Sunday, 9 April 2017 at 15.55
> To: "nginx@nginx.org"
> Subject: Mechanism to avoid restarting nginx upon ev
ilto:nginx-boun...@nginx.org>> on behalf
of Ajay Garg mailto:ajaygargn...@gmail.com>>
Reply-To: "nginx@nginx.org<mailto:nginx@nginx.org>"
mailto:nginx@nginx.org>>
Date: Sunday, 9 April 2017 at 15.55
To: "nginx@nginx.org<mailto:nginx@nginx.org>"
mai
Hi All.
We are wanting to implement a solution, wherein the user gets proxied to
the appropriate local-url, depending upon the credentials.
Following architecture works like a charm (thanks a ton to
fran...@daoine.org, without whom I would not have been able to reach here)
::