Return-Path: Delivered-To: apmail-xml-cocoon-users-archive@xml.apache.org Received: (qmail 87374 invoked by uid 500); 16 Jun 2003 19:41:02 -0000 Mailing-List: contact cocoon-users-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-users@xml.apache.org Delivered-To: mailing list cocoon-users@xml.apache.org Received: (qmail 87360 invoked from network); 16 Jun 2003 19:41:01 -0000 Received: from unknown (HELO ni-mail1.dna.utvinternet.net) (194.46.8.62) by daedalus.apache.org with SMTP; 16 Jun 2003 19:41:01 -0000 Received: from [192.168.42.6] (unverified [195.218.107.164]) by ni-mail1.dna.utvinternet.net (Vircom SMTPRS 2.1.255) with ESMTP id for ; Mon, 16 Jun 2003 20:41:04 +0100 Subject: Basic authentication From: Peter Flynn To: cocoon-users@xml.apache.org In-Reply-To: <20030616093832.62191.qmail@web20704.mail.yahoo.com> References: <20030616093832.62191.qmail@web20704.mail.yahoo.com> Content-Type: text/plain Organization: Silmaril Consultants Message-Id: <1055796006.3045.53.camel@lughnasadh.silmaril.ie> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 16 Jun 2003 21:40:06 +0100 Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I have failed to find anything in the docs about implementing crude Apache-style authentication (eg equivalent to .htaccess). We don't have any global auth framework yet, so the more sophisticated methods won't be applicable. The user requirement is simply to restrict some directories to user/psw pairs "like we did before" :-) Can someone point me at what I must have missed? I guess I could fake it up (although I don't know how to call crypt() from within an XSLT script) but I felt there is probably a better way... ///Peter --------------------------------------------------------------------- To unsubscribe, e-mail: cocoon-users-unsubscribe@xml.apache.org For additional commands, e-mail: cocoon-users-help@xml.apache.org