details: http://hg.nginx.org/njs/rev/214afa2466a0
branches:
changeset: 311:214afa2466a0
user: Igor Sysoev
date: Wed Feb 01 11:33:05 2017 +0300
description:
Added tag 0.1.9 for changeset 5bd283398822
diffstat:
.hgtags | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diffs
details: http://hg.nginx.org/njs/rev/c9308fed683e
branches:
changeset: 309:c9308fed683e
user: Igor Sysoev
date: Wed Feb 01 10:06:28 2017 +0300
description:
2017 year.
diffstat:
LICENSE | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diffs (12 lines):
diff -r 67d4bcb5
details: http://hg.nginx.org/njs/rev/5bd283398822
branches:
changeset: 310:5bd283398822
user: Igor Sysoev
date: Wed Feb 01 11:29:47 2017 +0300
description:
Version 0.1.9.
diffstat:
CHANGES | 38 ++
Makefile | 2 +-
2 files changed, 39 insert
30.01.2017 17:26, Maxim Dounin пишет:
Hello!
On Sat, Jan 28, 2017 at 02:08:29PM +0300, Matwey V. Kornilov wrote:
# HG changeset patch
# User Matwey V. Kornilov
# Date 1485600652 -10800
# Sat Jan 28 13:50:52 2017 +0300
# Branch fsize
# Node ID f3bb0258beb24b975b94966a94d45e9a9f5c3c39
# Pa
Hello!
On Tue, Jan 31, 2017 at 10:17:36AM -0800, Thibault Charbonnier wrote:
> On 1/31/17 8:00 AM, Maxim Dounin wrote:
> > You may want to provide more details on what problem you are
> > trying to solve.
>
> The use-case was originally to use a longer proxy_read_timeout on
> certain upstream l
Hello
> On Feb 1, 2017, at 4:54 AM, Maxim Dounin wrote:
>
> until there is a way to introduce variables
> support with less effort.
What do you suggest to reduce the patch size? Should it take care of those
other timeout directives in other modules?
One of my other hunch was to add the com
Hello!
On Wed, Feb 01, 2017 at 08:40:55AM -0800, Thibault Charbonnier wrote:
> > On Feb 1, 2017, at 4:54 AM, Maxim Dounin wrote:
> >
> > until there is a way to introduce variables
> > support with less effort.
>
> What do you suggest to reduce the patch size? Should it take
> care of those
# HG changeset patch
# User Tim Birkett
# Date 1485972846 -28800
# Thu Feb 02 02:14:06 2017 +0800
# Node ID 25129d5509b83f9c45a92c7508ebc1cd65592118
# Parent d2b2ff157da53260b2b1c414792100ff0cd1377d
Add ability to remove Connection header completely
In some cases it's desirable to strip res
On 2/1/17 8:58 AM, Maxim Dounin wrote:
I'm highly sceptical about introducing variables support
everywhere just to save some configuration complexity in very
special cases. In most cases there better ways to organize things
without using variables, as initial nginx configuration approach
suggest
