Why not just block the offending IP's ? Sent from my Verizon Wireless BlackBerry
-----Original Message----- From: Chad Morland <cmorl...@gmail.com> Date: Tue, 5 Apr 2011 13:00:02 To: <users@httpd.apache.org> Reply-To: users@httpd.apache.org Subject: [users@httpd] Full Request URI in access_log I've got a domain hosted on one of our servers that seems to be getting a ton of junk traffic from Bit Torrent clients. The request that is showing up in my access_log is: /announce...cedc031275%20430?info_hash=%CE%0Az%19%3C%3B~%84%2F.%8Cc%8A%DDyZ%C7%18%18%26&peer_id=-BC0109-%5E%02%B2%FDw%AB%19%DD%D9%BDxB&port=24668&natmapped=1&localip=192.168.1.11&port_type=wan&uploaded=0&downloaded=0&left=31457280&numwant=100&compact=1&no_peer_id=1&key=48054&event=started As you can see the full URI is not displayed after "announce". What is causing this to be clipped? I've tried different LogFormat options but nothing seems to display the full URI. I am trying to build a firewall content rule to reject access to this URL but I need to find out what the full request is. Thoughts?
