Hello, I would like to ask about this piece of code from function
ngx_ssl_shutdown:
n = SSL_shutdown(c->ssl->connection);
sslerr = 0;
/* before 0.9.8m SSL_shutdown() returned 0 instead of -1 on errors
*/
if (n != 1 && ERR_peek_error()) {
sslerr =
Hello!
On Mon, Dec 03, 2018 at 12:11:15PM +, Elliot Thomas wrote:
> This patch applies cache locking behaviour to stale cache entries, so
> in the case where the *_cache_lock directives are used, the same
> locking behaviour is used for stale content as it is for new entries.
>
>
Hello!
On Tue, Dec 04, 2018 at 05:00:10PM +0100, Jack Henschel wrote:
> From the current documentation it was not immediately obvious (at least
> to me and my colleague) that nginx does not set the $proxy_host variable
> to the hosts specified in an upstream block, but literally uses the name
>
Hello!
On Thu, Dec 06, 2018 at 06:42:23AM -0500, Andras Farkas wrote:
> On Wed, Nov 28, 2018 at 11:31 AM Maxim Dounin wrote:
> > Such a change will significantly modify typical rendering of error
> > pages, so I would rather refrain from it unless there are more
> > practical reasons than
Hello,
your path is very good. I tested it and works fine for as.
Reading complex value to the same local variable limit_rate was conflusing
for me at first time. But it is correct :)
if (r->limit_rate_after == 0
+&& clcf->limit_rate_after
+&&
