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:08, Grozdan wrote:
>>
>> 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 work
>>
>> Thanks :)
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx



--
Yours truly

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx