Hi, I've set my conf to deny illegal host headers, as per below option. However, I've noticed that bots from Google, Bing, Baidu, etc, when trying to fetch /robots.txt, often get blocked by nginx as it just terminates the connection with 444 response. Sometimes they succeed but more often they get blocked. Yes, I've checked to see if these bots are not impostors but they look legit to me. My nginby microchip - Nginx Mailing List - English
On Wed, Sep 3, 2014 at 5:13 PM, Grozdan <neutrino8@gmail.com> wrote: > On Wed, Sep 3, 2014 at 5:07 PM, Steve Wilson <lists-nginx@swsystem.co.uk> wrote: >> I've just thought of another angle for this. Is this hitting your >> default/only site? If it's got a host header you could create a site just >> for that that bins all requests off with a 444 and no logging. >by microchip - Nginx Mailing List - English
On Wed, Sep 3, 2014 at 5:07 PM, Steve Wilson <lists-nginx@swsystem.co.uk> wrote: > I've just thought of another angle for this. Is this hitting your > default/only site? If it's got a host header you could create a site just > for that that bins all requests off with a 444 and no logging. Yes, it's the only site. I will try what you suggested. Thanks! > > > On 02/09/2014by microchip - Nginx Mailing List - English
On Tue, Sep 2, 2014 at 3:09 PM, Maxim Dounin <mdounin@mdounin.ru> wrote: > Hello! > > On Tue, Sep 02, 2014 at 12:17:12PM +0100, Steve Wilson wrote: > >> Torrent clients have their own user agent normally, I had a need a while >> back to block some which we used the magic 444 to kill it. >> >> if ($http_user_agent ~* (uTorrent|Transmission) ) { >> reby microchip - Nginx Mailing List - English
On Tue, Sep 2, 2014 at 1:17 PM, Steve Wilson <lists-nginx@swsystem.co.uk> wrote: > Torrent clients have their own user agent normally, I had a need a while > back to block some which we used the magic 444 to kill it. > > if ($http_user_agent ~* (uTorrent|Transmission) ) { > return 444; > break; > > } Thanks. That seems to work here :) > > On 02/09/2014 12:0by microchip - Nginx Mailing List - English
Hi, Somehow my server gets hit by torrent requests which look like this: GET /?info_hash=..... after the = come long strings of seemingly random hashes torrent clients are looking for. I'd like to deny all such requests so would like if someone could provide me how to deny everything (and including) ?info_hash= I've looked all over the net at similar examples but all I tried thus far didn't wby microchip - Nginx Mailing List - English
Hi, I'm trying to convert the following Apache rewrite rule over to nginx rule. Can anybody help? thanks RewriteRule ^(.*)$ proxy.php?url=$1by microchip - How to...
Thanks :) and no, I'm not using Gallary2by microchip - Nginx Mailing List - English
Hi, I'm fairly new when it comes to nginx and would like to basically rewrite the following: /main.php --> index.php Can someone please give me an example how to do this? Thanksby microchip - Nginx Mailing List - English
Maxim Dounin Wrote: ------------------------------------------------------- > Hello! > > On Wed, Dec 22, 2010 at 12:44:48PM -0500, > microchip wrote: > > > oops, forgot the add the rewrite ^ > > http://somedomain.com:8080$request_uri? > permanent; in first server, but > > it doesn't work > > It won't as long as you still have "return 44by microchip - Nginx Mailing List - English
oops, forgot the add the rewrite ^ http://somedomain.com:8080$request_uri? permanent; in first server, but it doesn't workby microchip - Nginx Mailing List - English
hmm, it does not seem to work here. This is what I have so far, but when I add www at the beginning of the hostname, it can't find it. I should note that I'm using a hostname from DynDNS but I doubt that's an issue since I have used lighttpd in the past and it successfully rewrites server { listen *:8080 default_server; server_name _; return 444;by microchip - Nginx Mailing List - English
Oh, I see :) Thanks, will give it a try. Also bookmarked the site.by microchip - Nginx Mailing List - English
Hi, I'm trying to rewrite 'www.somedomain.com:8080' to 'somedomain.com:8080' but when I use the below, it doesn't work. Any ideas? :) if ($host != "somedomain.com:8080" ) { rewrite ^/(.*)$ "http://somedomain.com:8080/$1" permanent; }by microchip - Nginx Mailing List - English