rewrite last using variable

2013-10-27 Thread Ingo Schmidt
Hi, consider the following simplified nginx config snippet: set $var "/url?par=val"; location = /a { rewrite ^ $var redirect; } location = /b { rewrite ^ $var last; } location = /url { proxy_pass http://some_backend; } For location a the redirect goes via the client and everything w

Re: HttpLimitReqModule delivers "nginx/1.4.3" as a message for HTTP status code 429. Too generic!

2013-10-27 Thread Brian08275660
Hi Francis, Probably I shouldn't have said "malformed" when I chose a word to express the problem with the response. But I assumed that Nginx should show the phrase that corresponds to the code. I assumed that Nginx has been coded so it know that 429 means "Too Many Requests" and that we should re

Re: HttpLimitReqModule delivers "nginx/1.4.3" as a message for HTTP status code 429. Too generic!

2013-10-27 Thread Francis Daly
On Sun, Oct 27, 2013 at 09:45:40PM +0100, Lukas Tribus wrote: Hi there, > > What you have shown looks well-formed to me, but doesn't look as useful > > as you want. > > What is confusing is that when I do something similar, I get different > > output which does not look well-formed to me: > I t

Various debugging info not shown (

2013-10-27 Thread Alex
OK, I found out why sessions wouldn't be resumed after 3600s in my testings... it's not that nginx would have stopped caching the session, but it's the client. For example, openssl wouldn't cache sessions for longer than two hours: /ssl/t1_lib.c (same also for sslv3) long tls1_default_timeout

RE: HttpLimitReqModule delivers "nginx/1.4.3" as a message for HTTP status code 429. Too generic!

2013-10-27 Thread Lukas Tribus
Hi! > What you have shown looks well-formed to me, but doesn't look as useful > as you want. (They are different things. If it is a well-formed http > 429 response, then it is the client's job to know what that means. The > reason-phrase and the http body content are optional enhancements that >

Nagios check for nginx with separate metrics

2013-10-27 Thread Nikolaos Milas
Hello, I am trying to run a Nagios check for nginx (in Opsview Core) but I have a problem: All of the available (to my knowledge) nginx Nagios checks (http://exchange.nagios.org/directory/Plugins/Web-Servers/nginx/) produce comprehensive output which includes all "metrics" together, while I w

Re: HttpLimitReqModule delivers "nginx/1.4.3" as a message for HTTP status code 429. Too generic!

2013-10-27 Thread Francis Daly
On Sun, Oct 27, 2013 at 09:40:11AM -0400, Brian08275660 wrote: Hi there, > I think I'm actually reporting a malformed response, it is Nginx that send > "nginx/1.4.3" instead of something useful as "too many requests". This is quite confusing to me. What you have shown looks well-formed to me, b

Re: HttpLimitReqModule delivers "nginx/1.4.3" as a message for HTTP status code 429. Too generic!

2013-10-27 Thread Brian08275660
This is the output: root@ip-10-139-33-71:~# curl -v * About to connect() to api.xx.com port 80 (#0) * Trying 40.57.235.104... connected > GET /location/locate-ip?key=BBANBWEDS7UZ6FD8747F76VZ&ip=201.1.1.1 HTTP/1.1 > User-Agent: curl/7.22.0 (i686-pc-linux-gnu) libcurl/7.22.0 OpenSSL/

Various debugging info not shown (

2013-10-27 Thread Alex
Hi Maxim, Good question. I have been debugging a SSL configuration for some time, and one of the things I've been testing for is the renewal of session tickets. I used a thin client for that purpose: https://github.com/grooverdan/rfc5077 Anyhow, according to the test, session renewal appears

Re: HttpLimitReqModule delivers "nginx/1.4.3" as a message for HTTP status code 429. Too generic!

2013-10-27 Thread Jonathan Matthews
On 27 October 2013 13:40, Brian08275660 wrote: > I think I'm actually reporting a malformed response, it is Nginx that send > "nginx/1.4.3" instead of something useful as "too many requests". Please show the complete output of "curl -v <429-uri>". I don't see any visible output from a 429 with n

Re: Various debugging info not shown (

2013-10-27 Thread Maxim Dounin
Hello! On Sun, Oct 27, 2013 at 10:30:53AM +0100, Alex wrote: > I am trying to debug handshakes and ticket reuse. Lot's of debugging > information is shown in my error_log, but some info is skipped. > Specifically, info from: /src/event/ngx_event_openssl.c. For example, > > ngx_log_debug3(NGX_LOG

Re: HttpLimitReqModule delivers "nginx/1.4.3" as a message for HTTP status code 429. Too generic!

2013-10-27 Thread Brian08275660
Hi Francis, I think I'm actually reporting a malformed response, it is Nginx that send "nginx/1.4.3" instead of something useful as "too many requests". I have tested it with Firefox and there is no doubt. Also tested it with a java HTTP client component, the same result. The status code received

Re: HttpLimitReqModule delivers "nginx/1.4.3" as a message for HTTP status code 429. Too generic!

2013-10-27 Thread Francis Daly
On Sat, Oct 26, 2013 at 11:43:29PM -0400, Brian08275660 wrote: Hi there, > The module HttpLimitReqModule delivers "nginx/1.4.3" (at least with version > 1.4.3) as a message for the HTTP status code 429. That is too generic and > not useful at all. Are you reporting that nginx generates a malform

Various debugging info not shown (

2013-10-27 Thread Alex
Hi, I am trying to debug handshakes and ticket reuse. Lot's of debugging information is shown in my error_log, but some info is skipped. Specifically, info from: /src/event/ngx_event_openssl.c. For example, ngx_log_debug3(NGX_LOG_DEBUG_EVENT, c->log, 0, "ssl new session: %08XD:%d:%