Francis Daly Wrote: ------------------------------------------------------- > On Mon, Nov 18, 2013 at 02:49:27PM -0500, Nam wrote: > > Hi there, > > > I would like to see if it's possible to get limit_conn and limit_req > > working with the rewrite modules if statement. > > Not according to the current documentation. I know it's not in current documentaby Nam - Nginx Mailing List - English
Can you give an example of how I would accomplish the desired if statement I posted? I do not see how i could get map to do that myself.by Nam - Nginx Mailing List - English
To elaborate a bit more, in a single location I may end up with something like this... set $Whitelisted "No"; if ($GeoList1 = allow) { set $Whitelisted "Yes"; } if ($GeoList5 = allow) { set $Whitelisted "Yes"; } if ($http_user_agent ~ (googlebot|bingbot)) { set $Whitelisted "Yes"; } if ($Whitelisted ~* "No") { limit_coby Nam - Nginx Mailing List - English
Hello, I would like to see if it's possible to get limit_conn and limit_req working with the rewrite modules if statement. I have seen some discussion about this in the mailing list already saying to use stuff like throwing a 410 code and having that 410 code handled by a @named location that handles requests that should not be limited, such as ... location / { error_page 410 = @nolimit; ifby Nam - Nginx Mailing List - English
Thank you very much Igor and Maxim, I appreciate the help and the settings have indeed fixed the problem. Thanks again for both of you, and thanks for nginx.by Nam - Nginx Mailing List - English
Hi Guys, I have started getting this error on some of my servers today. I have an automated system which generates configuration files based upon how many customers we have. Our nginx servers currently run MANY sites (server directives) and all of a sudden we started getting the follow error when trying to do an nginx reload... : could not build the variables_hash, you should increase either vaby Nam - Nginx Mailing List - English
I have done a bunch of more testing, and so far, the geo module appears to be working, and this may be due to a configuration problem somewhere else.by Nam - Nginx Mailing List - English
Igor Sysoev Wrote: ------------------------------------------------------- > On Wed, Dec 01, 2010 at 01:23:17PM -0500, Nam > wrote: > > > You may enable the debug log for some addresses > only: > http://nginx.org/en/docs/debugging_log.html > Yes, I understand that, but in the past on our production boxes, we have found that simply having the --debug compilatiby Nam - Nginx Mailing List - English
I ran a test on the debug server, and I added an entry to the geo list to have the IP I was testing from. It got through our security without any problem. I know for a fact that it is not working properly though, perhaps load or memory is somehow causing problems with it on our other servers? The only difference between our test server and our production servers is the test server uses the --deby Nam - Nginx Mailing List - English
Igor Sysoev Wrote: ------------------------------------------------------- > On Wed, Dec 01, 2010 at 05:05:56AM -0500, Nam > wrote: > > > Hey Guys, I have run into a problem with the geo > module. I have set up a > > geo list containing a LARGE list of IPs which we > need to have > > "whitelisted" for getting through to the > upstream. Theseby Nam - Nginx Mailing List - English
Sorry, this is not the GeoIP module, rather it's the geo module.by Nam - Nginx Mailing List - English
Hey Guys, I have run into a problem with the geo module. I have set up a geo list containing a LARGE list of IPs which we need to have "whitelisted" for getting through to the upstream. These IPs are for search engines. Currently we have the list set up via the following way... geo $remote_addr $search { default 0; include geoip-search.conf; }by Nam - Nginx Mailing List - English
Thanks Igor, That appears to have taken care of it. Appreciate the help.by Nam - Nginx Mailing List - English
Any updates on this? I work with Payam, and if we update to newer version of nginx, we cannot get cookies passing to the upstream. Any assistance would be greatly appreciated. Thanks.by Nam - Nginx Mailing List - English
I had to make a change to the patch in order to get it working.... +if test -n "$USE_SYSLOG"; then instead of +if [[ "${USE_SYSLOG}" == "YES" ]]; then which got things working for me.by Nam - Nginx Mailing List - English
I have noticed that the patch on the gentoo site no longer works with the latest version of nginx. Does anyone know where you get an updated version of the patch?by Nam - Nginx Mailing List - English
Never mind guys, I found a work around. But honestly, this would be a really nice feature to add. Having the ability to customize the error log would be really handy. Thanks.by Nam - Nginx Mailing List - English
Hello Everyone, I need to be able to have access to live logs, so what I have done applied the syslog patch, which works wonderfully, but there is only problem. While I am able to customize the access_log format, the error_log format is non-customizable from what I can tell so far. I have set nginx up to log to syslog, which then sends the syslog records to a logging server. The logging serby Nam - Nginx Mailing List - English