Re: Fetching a string by parsing URL

2015-07-22 Thread sudharshanr
For some reason, I'm getting it as null. This is my config file: map $uri $last_path { ~*/(?[^/]+)/?$ $pathname; } server { listen 80; root /basefolder; error_page 500 501 502 503 504 = /error5x.html?name=$arg_name&path=$last_path; location ~*/error5x.html? { al

Re: Nginx 1.8 proxying to Netty - timeout from upstream

2015-07-22 Thread Maxim Dounin
Hello! On Tue, Jul 21, 2015 at 03:33:13PM -0400, smuthali wrote: > I have setup Nginx proxy to a Netty server. I am seeing a timeout from > upstream, i.e. Netty. The consequence of this timeout is that the JSON > payload response is truncated (as seen on browser developer tools) > > 2015/07/21

Tweak fastcgi_buffer

2015-07-22 Thread Karl Johnson
Hello, I need to tweak fastcgi_buffer to 1m on a website that has heavy requests to avoid buffer. If I use a distro with 4096 pagesize, is it better to do 256x 4k or 4x 256k? [root@web ~]# getconf PAGESIZE 4096 [root@web ~]# fastcgi_buffer_size 4k; fastcgi_buffers 256 4k; OR fastcgi_buffer_siz

Re: How to run nginx unit tests?

2015-07-22 Thread rms
Thanks Maxim. So from end user's perspective is there something I can do to test the validity of build/install? Posted at Nginx Forum: http://forum.nginx.org/read.php?2,260481,260489#msg-260489 ___ nginx mailing list nginx@nginx.org http://mailman.ngi

Doubt about killapache attack on nginx server

2015-07-22 Thread TASM
Hi, I am running nginx 1.0.11 standalone. Recently someone told me that my server is vulnerable to apache killer attack because when he run the following script, it shows "host seems vuln". I searched on this forum and found that "First of all, nginx doesn't favor HEAD requests with compression, so

Re: Fetching a string by parsing URL

2015-07-22 Thread Edho Arief
On Thu, Jul 23, 2015 at 2:08 AM, sudharshanr wrote: > I think I need to rephrase my question. Right now, my nginx.conf looks like > this: > > location ~*/path1/{ > if (-f $document_root/error503.html) { > return 503; > } > } > > error_page 503 ?arg1=$arg_queryparam1&arg2= from url> > > As you can

Re: How to run nginx unit tests?

2015-07-22 Thread Maxim Dounin
Hello! On Wed, Jul 22, 2015 at 01:48:31PM -0400, rms wrote: > Hello .. I just built and installed nginx on my Linux system. Are there any > unit/smoke/regression tests available to test the install? Our test suite is available at http://hg.nginx.org/nginx-tests/. It is designed for developers

How to run nginx unit tests?

2015-07-22 Thread rms
Hello .. I just built and installed nginx on my Linux system. Are there any unit/smoke/regression tests available to test the install? Thanks for your help. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,260481,260481#msg-260481 ___ nginx m

Re: Fetching a string by parsing URL

2015-07-22 Thread sudharshanr
I think I need to rephrase my question. Right now, my nginx.conf looks like this: location ~*/path1/{ if (-f $document_root/error503.html) { return 503; } } error_page 503 ?arg1=$arg_queryparam1&arg2= As you can see, if there is a 503 error, then I return a static file. The arguments to the stat

Re: Fetching a string by parsing URL

2015-07-22 Thread Payam Chychi
On Tuesday, July 21, 2015 at 9:43 PM, sudharshanr wrote: > I have a web server sitting behind Nginx. If there is an error, then I want > to fetch some information from the url and pass it on to a static file as > parameters. I have configured Nginx to fetch the query parameters from the > url u

Re: proxy_pass redirection

2015-07-22 Thread Payam Chychi
On Wednesday, July 22, 2015 at 2:26 AM, Puneeth Kumar wrote: > Hi, > I'm new to Nginx and we are using for reverse proxy. > > I'm able to configured Nginx and it's working but I've challenge in > configuring it for Dynamic proxy_pass. I've tried to use wild characters > in proxy_pass it's not w

proxy_pass redirection

2015-07-22 Thread Puneeth Kumar
Hi, I'm new to Nginx and we are using for reverse proxy. I'm able to configured Nginx and it's working but I've challenge in configuring it for Dynamic proxy_pass. I've tried to use wild characters in proxy_pass it's not working, please help. E.G. location server { #listen 443; listen 808