Full Request URI in access_log

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: users@xxxxxxxxxxxxxxxx
Subject: Full Request URI in access_log
From: Chad Morland <cmorland@xxxxxxxxx>
Date: Tue, 5 Apr 2011 13:00:02 -0400
Reply-to: users@xxxxxxxxxxxxxxxx

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?

Follow-Ups:
- Re: Full Request URI in access_log
  - From: Daniel Reinhardt
- Re: Full Request URI in access_log
  - From: Yehuda Katz

Prev by Date: Reverse Proxy with Apache. CAS + two tomcat servers.
Next by Date: Re: Full Request URI in access_log
Previous by thread: Reverse Proxy with Apache. CAS + two tomcat servers.
Next by thread: Re: Full Request URI in access_log
Index(es):
- Date
- Thread

[Index of Archives] [Open SSH Users] [Linux ACPI] [Linux Kernel] [Linux Laptop] [Kernel Newbies] [Security] [Netfilter] [Bugtraq] [Squid] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Samba] [Video 4 Linux] [Device Mapper]