Re: strange map $request issue

2014-06-20 Thread itpp2012
It was a malformed request so a 400 is correct, a valid HEAD in this case does return a 412. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,251074,251080#msg-251080 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listi

Re: strange map $request issue

2014-06-20 Thread Maxim Dounin
Hello! On Fri, Jun 20, 2014 at 09:35:20AM -0400, itpp2012 wrote: > The log entries are both in access.log, nothing in error.log, maybe a > try_files thing ? though the IF is after try_files and works for a GET. Note that you have to configure error_log to log "info" level messages. By default,

Re: strange map $request issue

2014-06-20 Thread itpp2012
The log entries are both in access.log, nothing in error.log, maybe a try_files thing ? though the IF is after try_files and works for a GET. Posted at Nginx Forum: http://forum.nginx.org/read.php?2,251074,251076#msg-251076 ___ nginx mailing list nginx

Re: strange map $request issue

2014-06-20 Thread Maxim Dounin
Hello! On Fri, Jun 20, 2014 at 09:05:44AM -0400, itpp2012 wrote: > For example: > > map $request $testvar { > default 0; > ~*montytest 1; > } > > if ($testvar) { return 412; } > > [20/Jun/2014:xx:xx:20 +0200] 69.64.:

strange map $request issue

2014-06-20 Thread itpp2012
For example: map $request $testvar { default 0; ~*montytest 1; } if ($testvar) { return 412; } [20/Jun/2014:xx:xx:20 +0200] 69.64.:52393 - - "GET /montytest/ HTTP/1.1" 412 712 "-" "Mozilla/5.0 [20/Jun/2014:xx: