From owner-freebsd-isp Mon Nov 24 17:26:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA23088 for isp-outgoing; Mon, 24 Nov 1997 17:26:28 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA23077 for ; Mon, 24 Nov 1997 17:26:23 -0800 (PST) (envelope-from marcs@znep.com) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.7/8.8.7) with UUCP id SAA00274; Mon, 24 Nov 1997 18:26:01 -0700 (MST) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id SAA06011; Mon, 24 Nov 1997 18:24:26 -0700 (MST) Date: Mon, 24 Nov 1997 18:24:26 -0700 (MST) From: Marc Slemko To: Peter Olsson cc: Eddie Fry , isp@FreeBSD.ORG Subject: Re: Web Page Restrictions In-Reply-To: <3.0.32.19971125013534.0068bdf4@lda> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id RAA23084 Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 25 Nov 1997, Peter Olsson wrote: > 16:53 1997-11-24 -0700 Eddie Fry wrote: > >I'm running 2.2.2 and Apache. I have a customer that keeps putting up > pages that should be in his own domain (we host a domain for him). Is > there a way to "turn-off" the üxxx link to a certain user's page? > > Make his web-directory (default public_html) owned by root, > chmod it to 700 and delete all his files in the directory. I'm afraid that won't do much. All he has to do is remove the directory and make a new one. You can make it immutable, but you don't want to do that unless you want to. In Apache 1.3, you can disable specific ~userdirs. See the mod_userdir docs for details. You can't do this in 1.2. Otherwise, you can add something like: deny from all AllowOverride none to your config file. /home/user has to be what ~user is. It may be /usr/home or /home or something else in your passwd file. It must be what is in the passwd file, it is not enough for it to be a symlink to the same place.