Rewrite directory lookup to another directory

Hello All, I am trying to add a rewrite rule to my nginx configuration. But each time it is giving me 404/302 error. My scenarios is given below 1. If someone request URL http://192.168.44.163/testa or http://192.168.44.163/testa/ then it should be redirected to http://192.168.44.163/testa/web/in

Re: Use of boringssl equal-preference cipher groups with nginx

thanks Alex so what's the updated way to compile Nginx against BoringSSL ? Posted at Nginx Forum: http://forum.nginx.org/read.php?2,252640,252779#msg-252779 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx

Documentation of limit_req

About http://nginx.org/en/docs/http/ngx_http_limit_req_module.html It does not specify anything about inheritance. It appears (from reading sources) that limit_req are inherited only, if no new limit_req are specified. This is the same as for proxy_set_header and others: http://nginx.org/en/d

Re: Use of boringssl equal-preference cipher groups with nginx

Hi again, On 2014-08-18 09:17, Alex wrote: 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. [...] Would this already work with nginx' ssl_ciphers parame

Hello - and missing verification of configuration format / very tiny mem leak in limit_req config

Hi, My name is Martin. I am new to this list (obvious), and new to nginx as well. I hope this is the right place for the feedback I have, if not please correct me. Well the below may be for the bugtracker. Except: It is yet to be confirmed as bug, I was unable to find a way to register. (I do