From owner-freebsd-questions Tue Oct 14 10:40:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA04408 for questions-outgoing; Tue, 14 Oct 1997 10:40:19 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA04398 for ; Tue, 14 Oct 1997 10:40:13 -0700 (PDT) (envelope-from dwhite@gdi.uoregon.edu) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id KAA02559; Tue, 14 Oct 1997 10:39:41 -0700 (PDT) Date: Tue, 14 Oct 1997 10:39:41 -0700 (PDT) From: Doug White Reply-To: Doug White To: Enrique Krajmalnik cc: freebsd-questions@FreeBSD.ORG Subject: Re: Password protected web site In-Reply-To: <3442F836.698@illumen.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 13 Oct 1997, Enrique Krajmalnik wrote: > I am having two problems setting up a web site with password protection. > > 1. I have added the -lcrypt option under CFLAGS to compile the htpasswd > file. It no longer reports any error messages when it compiles. However, > when I try to execute it, I get a bad command or file name message. Any > quick ideas on this? the htpasswd binary isn't in your path or you need to update your sell. Try running `rehash' or give the explicit path to the htpasswd executable. > 2. I have modified the access.conf file, created an .htaccess file in > the directory I wish to protect, and created an htpasswd file (using the > web interface at euronet). I can access the site and it will propmpt for > a username and password; it will properly authorize the user and bring > up the web page. However, it only does this the first time the page is > accessed. The browser must be exited and restarted for the pasword > prompt to reappear. I am sure there is a simple fix for this. The browser isprobably caching the page and thus doesn't have to ask the web server for the page again and go through authentication. I bet that the browser is caching the username and password too. If you cleared out the memory & disk cache you'd have to authenticate again. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major