Received: from bubbles.electricutopia.net (bubbles.electricutopia.net [63.214.178.76]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2DJtSx85741 for ; Tue, 13 Mar 2001 14:55:28 -0500 (EST) (envelope-from dave@slickness.org) Received: from localhost (dave@localhost) by bubbles.electricutopia.net (8.9.3/8.9.3) with ESMTP id LAA30508; Tue, 13 Mar 2001 11:50:45 -0800 Date: Tue, 13 Mar 2001 11:50:45 -0800 (PST) From: David Olbersen X-X-Sender: To: Michael Fork cc: , Paul Joseph McGee , Subject: Re: Re: Secure pages In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200103/12 X-Sequence-Number: 196 On Tue, 13 Mar 2001, Michael Fork wrote: ->not if the include file ends with a .php -- since it is in , anybody ->acessing the file from a web browser would not be able to see it. I misunderstood, I thought you meant that you would put that code in an included file. Which anybody could get at. However the code being hidden doesn't change that I could look for a cookie from your domain, see it's value, and still create another cookie. What you're all looking for is a *session based* authentication system. PHP does this, and you can do it yourself if you have a database set up. -- Dave