details: http://hg.nginx.org/njs/rev/c0aa3ecd2e83
branches:
changeset: 163:c0aa3ecd2e83
user: Igor Sysoev
date: Wed Aug 31 15:53:13 2016 +0300
description:
An invalid value of Date object has been fixed.
diffstat:
njs/njs_date.c | 10 ++
njs/test/njs_unit_test.c
details: http://hg.nginx.org/njs/rev/47f4830c3d22
branches:
changeset: 162:47f4830c3d22
user: Igor Sysoev
date: Tue Aug 30 12:11:24 2016 +0300
description:
C language features have been enabled.
diffstat:
nxt/auto/clang | 86 +++
details: http://hg.nginx.org/njs/rev/323f00dc9879
branches:
changeset: 161:323f00dc9879
user: Igor Sysoev
date: Tue Aug 30 12:05:46 2016 +0300
description:
decodeURI() and decodeURIComponent() functions.
diffstat:
njs/njs_builtin.c|4 +
njs/njs_generator.c |2
details: http://hg.nginx.org/njs/rev/d63ecb57f164
branches:
changeset: 160:d63ecb57f164
user: Igor Sysoev
date: Tue Aug 30 12:02:31 2016 +0300
description:
encodeURI() and encodeURIComponent() functions.
diffstat:
njs/njs_builtin.c| 16 +++--
njs/njs_generator.c |
Hello,
I am using nginx primarily as a proxy and I am looking to improve the
visibility and control over keepalive connections to upstreams.
I have several patches I would like to submit for your consideration
but I am relatively unfamiliar with the code base so I've started
simple and I apprecia
details: http://hg.nginx.org/njs/rev/76f16f0ef6c5
branches:
changeset: 164:76f16f0ef6c5
user: Igor Sysoev
date: Wed Aug 31 17:51:54 2016 +0300
description:
A fix in decodeURI() and decodeURIComponent() functions.
diffstat:
njs/njs_string.c | 1 +
1 files changed, 1 insertions(+),
details: http://hg.nginx.org/njs/rev/584114a51b51
branches:
changeset: 165:584114a51b51
user: Igor Sysoev
date: Wed Aug 31 19:18:47 2016 +0300
description:
A fix in decodeURI() function.
diffstat:
njs/njs_string.c | 6 --
1 files changed, 4 insertions(+), 2 deletions(-)
diff
details: http://hg.nginx.org/njs/rev/715b147cbfe0
branches:
changeset: 166:715b147cbfe0
user: Igor Sysoev
date: Wed Aug 31 19:28:08 2016 +0300
description:
A fix in decodeURI() and decodeURIComponent() functions.
diffstat:
njs/njs_string.c | 6 +++---
1 files changed, 3 insertion
Hello!
On Wed, Aug 31, 2016 at 01:19:14AM +0800, 洪志道 wrote:
> Hi.
>
> It’s do really a funny experience. Now I use in the following way.
>
> [ngx_http_hello_module]
>
>
> 1. development:
>
> ngx_http_hello_module.c => ngx_http_hello_module.so
>
>
> 2. production
>
> mv modules/ngx_http_h
# HG changeset patch
# User Josh Yudaken
# Date 1472606412 25200
# Tue Aug 30 18:20:12 2016 -0700
# Node ID f81a22addc7fe1ca7486e932470756f4d73a3bb2
# Parent c6372a40c2a731d8816160bf8f55a7a50050c2ac
Add --without-http-expect option
Some load balancers (specifically Google Cloud) do not supp
# HG changeset patch
# User Josh Yudaken
# Date 1472606412 25200
# Tue Aug 30 18:20:12 2016 -0700
# Node ID f81a22addc7fe1ca7486e932470756f4d73a3bb2
# Parent c6372a40c2a731d8816160bf8f55a7a50050c2ac
Add --without-http-expect option
Some load balancers (specifically Google Cloud) do not supp
Hello!
On Wed, Aug 31, 2016 at 10:08:44AM -0700, Josh Yudaken wrote:
> # HG changeset patch
> # User Josh Yudaken
> # Date 1472606412 25200
> # Tue Aug 30 18:20:12 2016 -0700
> # Node ID f81a22addc7fe1ca7486e932470756f4d73a3bb2
> # Parent c6372a40c2a731d8816160bf8f55a7a50050c2ac
> Add --wi
Hi,
I wasn't sure of any other examples of it breaking the HTTP standard,
so figured a compile time option was safer. Unfortunately bugging
Google any more than we already do probably won't get the problem
solved, and the standard "100 Continue" behavior causes 502 errors for
our end users.
For r
Hey Maxim,
> At this point nginx just uses the interface provided by the
> OpenSSL library, exactly as documented. The fact that the
> interface is flawed (and documented to be flawed to make sure
> people will use it properly) has nothing to do with nginx use of
> it.
And yet, NGINX doesn't use
Thanks
2016-09-01 0:50 GMT+08:00 Maxim Dounin :
> Hello!
>
> On Wed, Aug 31, 2016 at 01:19:14AM +0800, 洪志道 wrote:
>
> > Hi.
> >
> > It’s do really a funny experience. Now I use in the following way.
> >
> > [ngx_http_hello_module]
> >
> >
> > 1. development:
> >
> > ngx_http_hello_module.c => ng
Hey Maxim,
> Could you please describe one of the uses cases in details?
> That's what I'm asking all the time, and still didn't get even a
> single description of a real-world use case.
You were definitely given some real-world use cases in this thread already:
http://mailman.nginx.org/pipermai
16 matches
Mail list logo