Re: Question about proxy_cache_key

2017-02-15 Thread Dewangga Bachrul Alam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Example: [dominique@galea ~]$ curl -I "http://networksninja/artikel/berita/a-pen-by-hair"; HTTP/1.1 200 OK Server: networksninja Date: Thu, 16 Feb 2017 06:48:13 GMT Content-Type: text/html; charset=UTF-8 Connection: keep-alive Vary: Accept-Encoding

Question about proxy_cache_key

2017-02-15 Thread Dewangga Bachrul Alam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello! I've compiled latest nginx 1.11.10 with ngx_cache_purge, my configurations likes: proxy_cache_key "$uri$is_args$args"; proxy_cache_path /var/cache/nginx/proxy_cache levels=1:2 keys_zone=networksninja_cache:60m inactive=60m use_temp_path=off

swapiness value to be set for high load nginx server

2017-02-15 Thread omkar_jadhav_20
Hi, We are using nginx/1.10.2 as web server on centos and redhat Linux 7.2 OS. We are getting issues of getting our SWAP fully utilized even though we have free memory , vm.swapiness is kept as default i.e. 60. below are memory details for your reference : # free -g totaluse

potential null dereference

2017-02-15 Thread al...@sbrella.com
Hi， In file /src/http/ngx_http_upstream.c, function ngx_http_upstream_finalize_request // if u->pipe == NULL, ngx_http_file_cache_free(r->cache, u->pipe->temp_file); will dereference a null pointer, it's that right ? // Regards // Alex if (u->store && u->pipe && u->pipe->temp_file

Client certificate fails with "unsupported certificate purpose" from iPad, works in desktop browsers

2017-02-15 Thread nrahl
We have client certificates set up and working for desktop browsers, but when using the same certificates that work on the desktop browser from an iPad, we get a "400: The SSL certificate error" in the browser, and the following in the log: "18205#18205: *11 client SSL certificate verify error: (2

reverse proxy with TLS-PSK

2017-02-15 Thread Bruno De Maesschalck
Hey, For our application we want embedded devices to access backend websocket/http services through nginx with TLS/SSL. The embedded devices are very resource constraint and would benefit from using TLS-PSK. My question is does nginx support reverse proxy and using TLS-PSK to secure incoming c

input required on proxy_next_upstream

2017-02-15 Thread Kaustubh Deorukhkar
Hi, We are using nginx as reverse proxy and have a set of upstream servers configured with upstream next enabled for few error conditions to try next upstream server. For some reason this is not working. Can someone suggest if am missing something? http { ... upstream myservice { server loc

Re: nginx-1.11.10

2017-02-15 Thread Руслан Закиров
On Tue, Feb 14, 2017 at 6:52 PM, Maxim Dounin wrote: > *) Feature: the "proxy_cache_background_update", >"fastcgi_cache_background_update", "scgi_cache_background_update", >and "uwsgi_cache_background_update" directives. > Sounds so sexy :) Blog post? docs? -- Руслан Закир

Re: nginx-1.11.10

2017-02-15 Thread Руслан Закиров
On Tue, Feb 14, 2017 at 6:52 PM, Maxim Dounin wrote: > *) Bugfix: a segmentation fault might occur in a worker process when >using AIO after an "X-Accel-Redirect" redirection. > Thank you. Been bothering us a lot... -- Руслан Закиров Руководитель отдела разработки веб-сервисов +7(

Re: nginx-1.11.10

2017-02-15 Thread Anoop Alias
*_cache_background_update - What does it do? On Tue, Feb 14, 2017 at 9:22 PM, Maxim Dounin wrote: > Changes with nginx 1.11.10 14 Feb > 2017 > > *) Change: cache header format has been changed, previously cached >responses will be invalidated. >

Re: input required on proxy_next_upstream

2017-02-15 Thread Maxim Dounin
Hello! On Wed, Feb 15, 2017 at 01:27:53PM +0530, Kaustubh Deorukhkar wrote: > We are using nginx as reverse proxy and have a set of upstream servers > configured > with upstream next enabled for few error conditions to try next upstream > server. > For some reason this is not working. Can someone