Re: Exclude ip's from Nginx limit_req zone

2014-12-24 Thread ASTRAPI
Thanks for your reply Maxim Dounin So something like this ? : Main nginx conf: http { geo $limited { default 1; 192.168.45.56/32 0; 199.27.128.0/21 0; 173.245.48.0/20 0; 103.21.244.0/22 0; 103.22.200.0/22 0; 103.31.4.0/2

Re: Serve different pages for different IP

2014-12-24 Thread Francis Daly
On Wed, Dec 24, 2014 at 10:16:28AM -0500, magal wrote: Hi there, > My configuration would be to have one document_root for a specific IP and > another for the rest of the world. In each case, do not set $document_root. Instead, set $my_root_var (for example). Then separately, do root $my_roo

Re: [nginx-announce] nginx-1.7.9

2014-12-24 Thread Kevin Worthington
Hello Nginx users, Now available: Nginx 1.7.9 for Windows http://goo.gl/DsVDe5 (32-bit and 64-bit versions) These versions are to support legacy users who are already using Cygwin based builds of Nginx. Officially supported native Windows binaries are at nginx.org. Announcements are also availab

Re: Serve different pages for different IP

2014-12-24 Thread magal
Thank you. My configurations were: 1. root /path_to_root1; if ($remote_addr = xx.xx.xx.xx) { set $document_root /path_to root2; } 2. map $remote_addr $document_root { default /path_to_root1; xx.xx.xx.xx /path_to root2; } 3. geo $document_root { default /path_to_root1; xx.xx.xx

Re: Exclude ip's from Nginx limit_req zone

2014-12-24 Thread Maxim Dounin
Hello! On Wed, Dec 24, 2014 at 09:01:09AM -0500, ASTRAPI wrote: > Anyone please? An example of how to whitelist addresses from limit_req can be found in the mailing list archives, for example here: http://mailman.nginx.org/pipermail/nginx/2012-July/034790.html Documentation on directives used

Re: Exclude ip's from Nginx limit_req zone

2014-12-24 Thread ASTRAPI
Anyone please? Posted at Nginx Forum: http://forum.nginx.org/read.php?2,255697,255773#msg-255773 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Re: Big file upload through proxy problem

2014-12-24 Thread Maxim Dounin
Hello! On Tue, Dec 23, 2014 at 02:17:38PM -0500, Guest13778 wrote: > Sorry, I forgot to post an example: > > # curl -v -F file=@test.tar.gz -T http:/mydomain.com > * About to connect() to mydomain.com port 80 (#0) > * Trying 192.168.15.1... connected > * Connected to mydomain.com (192.168.15.1

Re: OCSP_check_validity() status expired

2014-12-24 Thread Maxim Dounin
Hello! On Wed, Dec 24, 2014 at 06:48:00AM -0500, khav wrote: > I am seeing a lot of these errors in my /var/log/nginx/error.log > > [error] 11405#0: OCSP_check_validity() failed (SSL: error:2707307D:OCSP > routines:OCSP_check_validity:status expired) while requesting certificate > status, respo

Re: OCSP_check_validity() status expired

2014-12-24 Thread ionsec
hi khav, try adding the following lines to your nginx website configuration file: ssl_stapling on; ssl_stapling_verify on; ssl_trusted_certificate /etc/nginx/my_ssl_certs/ca-bundle.pem; # # note the PEM encoded X509 ca-bundle file should contain the ssl certificate # chain

OCSP_check_validity() status expired

2014-12-24 Thread khav
I am seeing a lot of these errors in my /var/log/nginx/error.log [error] 11405#0: OCSP_check_validity() failed (SSL: error:2707307D:OCSP routines:OCSP_check_validity:status expired) while requesting certificate status, responder: ocsp2.globalsign.com How can i fix that Posted at Nginx Forum:

Re: Ignore content-type while forwarding to backend proxy

2014-12-24 Thread Francis Daly
On Wed, Dec 24, 2014 at 08:53:13AM +0200, Roland RoLaNd wrote: Hi there, > i tried doing that before though it did not work so i thought there could be > another solution..in any case tried that again, set it right before the > proxypass condition and it's still passing the type through...may i