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 f2DJRsx81687 for ; Tue, 13 Mar 2001 14:27:55 -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 LAA30404; Tue, 13 Mar 2001 11:24:03 -0800 Date: Tue, 13 Mar 2001 11:24:03 -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/10 X-Sequence-Number: 194 On Tue, 13 Mar 2001, Michael Fork wrote: ->The easiest way in PHP that I have found is to create a file called ->validate.php containing the following: -> -> if ($HTTP_COOKIE_VARS["MyCookie"] != 'Some Value') { -> header("Location: http://my.company.com/login"); -> } ->?> -> ->and, after the user has logged in, set a cookie. Then, for each page that ->should be for a logged-in user only, just include the validate.php file. Boy that's not very secure...I could find your included file, see what 'Some Value' is, and then just make my own cookie! -- Dave