From owner-freebsd-questions Thu Jun 6 11:21:31 2002 Delivered-To: freebsd-questions@freebsd.org Received: from cactus.fi.uba.ar (cactus.fi.uba.ar [157.92.49.108]) by hub.freebsd.org (Postfix) with ESMTP id 0D11B37B40A for ; Thu, 6 Jun 2002 11:21:12 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by cactus.fi.uba.ar (8.11.6/8.11.6) with ESMTP id g56IIn795095; Thu, 6 Jun 2002 15:18:49 -0300 (ART) (envelope-from fgleiser@cactus.fi.uba.ar) Date: Thu, 6 Jun 2002 15:18:49 -0300 (ART) From: Fernando Gleiser X-X-Sender: To: Sheldon Hearn Cc: Subject: Re: Sniffing HTTP requests off the wire In-Reply-To: <3545.1023358851@axl.seasidesoftware.co.za> Message-ID: <20020606151525.U82269-100000@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 6 Jun 2002, Sheldon Hearn wrote: > > Hi folks, > > > I'm interested in the HTTP request and the IP address of the requesting > host. I'm also interested in the HTTP headers( like referer), cookie > contents etc, but that's all secondary. > > I know I can just use 'tcpdump -s 1500 -x -X dst port 80' and > cook the output myself, but I'm hoping there's already something out > there that does the cooking for me. Install tcpshow and it will cook the tcpdump output for you. I use it and works like a charm, but you won't get CLF output Fer > > First prize would be to get output in common log format, as used by > Apache, but obviously beggars can't be choosers. > > Anything in the ports tree? > > Ciao, > Sheldon. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message