From owner-freebsd-www Thu Dec 31 08:27:20 1998 Return-Path: Received: (from daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16654 for www-outgoing; Thu, 31 Dec 1998 08:27:20 -0800 (PST) (envelope-from owner-freebsd-www) Received: from baerenklau.de.freebsd.org (baerenklau.de.freebsd.org [195.185.195.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16649 for ; Thu, 31 Dec 1998 08:27:18 -0800 (PST) (envelope-from wosch@panke.de.freebsd.org) Received: (from uucp@localhost) by baerenklau.de.freebsd.org (8.8.8/8.8.8) with UUCP id RAA05833 for www@freebsd.org; Thu, 31 Dec 1998 17:26:58 +0100 (CET) (envelope-from wosch@panke.de.freebsd.org) Received: (from wosch@localhost) by campa.panke.de.freebsd.org (8.8.8/8.8.8) id RAA20661 for www@freebsd.org; Thu, 31 Dec 1998 17:14:48 +0100 (MET) (envelope-from wosch) Message-ID: <19981231171446.B20173@panke.de.freebsd.org> Date: Thu, 31 Dec 1998 17:14:47 +0100 From: Wolfram Schneider To: www@FreeBSD.ORG Subject: blocking URLs with leading slashes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i Sender: owner-freebsd-www@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk An "unfriendly" and buggy robot visited www.freebsd.org and requested 30.000 URLs/day with leading slashes, e.g. ///////handbook/ I'm now blocking URLs with leading slashes. URLs with 2 leading slashes get a redirect to a URL with only one slash, e.g. // -> / //handbook/ -> /handbook/ URLs with 3 ore more leading slashes get a access forbidden message. /// -> forbidden ///////handbook/ -> forbidden -- Wolfram Schneider http://freebsd.org/~w/