http {
resolver 127.0.0.1;
resolver_timeout 1s;
server {
listen 8000;
location /test {
proxy_pass http://$arg_host:8080;
}
}
server {
listen 8080;
...
}
}
ps: other configure is normal
I have recently discoverd that wh
anyone ? Help please. I am pretty much stuck. Thanks
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,252597,252660#msg-252660
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
I have added support for two way /mutual SSL authentication support.
https://github.com/nginx/nginx/pull/7
http://mailman.nginx.org/pipermail/nginx-devel/2014-August/005817.html
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,245971,252658#msg-252658
__
On 18 Aug 2014, at 14.22, Valentin V. Bartenev wrote:
> On Monday 18 August 2014 13:45:46 Jason Woods wrote:
> [..]
>> There's the fear there are significant changes from 1.6 to 1.7 that may
>> introduce other problems, and would need to go through some extensive
>> testing before we can commit.
On Monday 18 August 2014 13:45:46 Jason Woods wrote:
[..]
> There's the fear there are significant changes from 1.6 to 1.7 that may
> introduce other problems, and would need to go through some extensive
> testing before we can commit. Especially as the 1.6 is labelled "stable" and
> the 1.7 "mainl
If its only a few lines you may consider adding the patch manually.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251779,252648#msg-252648
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
On Mon, Aug 18, 2014 at 2:45 PM, Jason Woods wrote:
>
> There's the fear there are significant changes from 1.6 to 1.7 that may
> introduce other problems, and would need to go through some extensive
> testing before we can commit. Especially as the 1.6 is labelled "stable"
> and the 1.7 "mainlin
On Sun, Aug 17, 2014 at 02:37:46PM +0800, ywsample wrote:
> I know nginx 1.7.4 fixes a bug about DNS resolver, but i do not quite
> understand why this would lead to a request hang, Because there is a
> timeout handling, at a specified time if there is no response the timeout
> callback will be cal
On 18 Aug 2014, at 12.05, Valentin V. Bartenev wrote:
> On Monday 18 August 2014 11:40:07 Jason Woods wrote:
> [..]
>>
>> I'm experiencing a similar issue.
>>
>> I get a couple of ident mismatch errors in the error log,
>> and then gradually over time I begin to see thousands of
>> ESTABLISHED
On Monday 18 August 2014 11:40:07 Jason Woods wrote:
[..]
>
> I'm experiencing a similar issue.
>
> I get a couple of ident mismatch errors in the error log,
> and then gradually over time I begin to see thousands of
> ESTABLISHED connections stuck with no activity.
> Eventually worker_connection
Hi,
On 16 Jul 2014, at 03.01, Pramod Korathota wrote:
> On 15 July 2014 21:41, Ruslan Ermilov wrote:
>
>
> diff --git a/src/core/ngx_resolver.c b/src/core/ngx_resolver.c
> --- a/src/core/ngx_resolver.c
> +++ b/src/core/ngx_resolver.c
>
>
>
> Thanks for the quick response and patch, Rusla
Hi,
I have successfully compiled nginx/1.7.4 with boringssl. One thing I am
not sure if it's possible already is to take advantage of
equal-preference cipher groups that Boringssl supports. For reference:
https://www.imperialviolet.org/2014/02/27/tlssymmetriccrypto.html
https://boringssl.goo
12 matches
Mail list logo
