6

How to block Nginx access log statements from specific user agents

view full story
linux-howto

http://serverfault.com – I am looking to turn off logging in the Nginx access log file from specific requests from http user agents. Basically from the Amazon ELB Health Check and our external (Pingdom) monitoring. Since these come every few seconds, makes testing hard to sort through the logs. "GET / HTTP/1.1" 200 727 "-" "ELB-HealthChecker/1.0" "GET /login HTTP/1.1" 200 7492 "-" "Pingdom.com_bot_version_1.4_(http://www.pingdom.com/)" I was able to block logging for image files, but have not seen anything for incoming requests: location ~* ^.+.(jpg|jpeg|gif|css|png|js|ico|xml|svg)$ { access_log (HowTos)

taskli's picture
Submitted by taskli on 08/03/2012 – Made popular on 08/03/2012

Stories similar to How to block Nginx access log statements from specific user agents

Website uptime monitoring firm Pingdom has been looking at visitor stats to find out where Macs are most popular. Australia is one of the top ten nations on this measure.

Some interesting statistics have been published by Pingdom, and although we may not agree with some of them, we thought to share them with you.

The first data put forward by Pingdom is about the popularity of various Linux distributions. The first place is occupied by Linux Mint, followed by Mageia and Ubuntu.

Filed under: Internet, Security

As far as I can see Nginx supports by default 2 log files: error_log (tracks issues related to the Nginx server itself) and access_log (tracks requests processed by Nginx).

nginx: How To Block Exploits, SQL Injections, File Injections, Spam, User Agents, Etc.

This short article explains how you can block the most common exploits, SQL injections, file injections, spam and user agents used by hackers and bandwidth hoggers from your nginx vhosts with some simple configuration directives.

I am in the process of trying to configure a Server with https and for some reason it seems the requests are not hitting nginx at all. I have everything working properly but once I go to enable ssl it gives me an will not accept any requests on port 443 (connection timeout). Does anyone know how I can begin to debug this issue? I am using all of the same logic I have used on previous servers.

I have a server hosted at my end, I am monitoring the server with pingdom and also my router. Strange thing is the response time towards the router is fine, but when the traffic flows towards the server, the response time became relatively high. Its more than 1000ms. Can anyone help me with it?

Thanks.

Monitoring IP Restrictions 19 weeks 6 days ago

Let's say we have web servers that are behind a firewall. There are some IP limitations rules applied to the firewall, for several ports / protocols :

SSH, SFTP, SSH Some Web applications (specific port, for instance http://www.application-example.com:8080/)

These are settings, and sometimes they get messed up for X reasons (human interventions or system failure, etc ...)

Is there any serv

The software company I work for would like to monitor how long it takes to download their installers (hosted in several locations and about 30-100mb each) from various countries around the world.

I am aware of website monitoring services like Pingdom and Site24x7, and have contacted their customer services, but neither have the facility to monitor download times of such large files via HTTP.

For