Re: Cookies & sessions
| From: | tedd | Date: | Fri, 22 Jan 2010 16:25:56 +0000 |
| Subject: | Re: Cookies & sessions | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-301355@lists.php.net to get a copy of this message | ||
At 8:58 AM +1100 1/22/10, clancy_1@cybec.com.au wrote:
On Thu, 21 Jan 2010 08:54:44 -0500, tedd.sperling@gmail.com (tedd) wrote:Clancy: My advise -- don't use Cookies to control access for anything. Cookies are client-side and you should never trust anything coming from the client. If you want to protect access to a private portion of your site, then require a user id and password. Using Cookies to do that is vary dangerous. Cheers, tedd -- ------- http://sperling.com http://ancientstones.com http://earthstones.comAt 12:15 PM +1100 1/21/10, clancy_1@cybec.com.au wrote:Well, I hope this information is helpful.On Wed, 20 Jan 2010 20:05:42 -0200, bsfajardo@gmail.com (Bruno Fajardo) wrote:Yes; I'm doing that too. I am setting up a private website, and using cookies to control access to it. ClancyYes, thanks to everyone who contributed. I now have a better understanding of what cookies are, and have turned on output buffering, enabling me to put the handler where I want, and still be able to debug it. ClancyOne last thing. I use sessions for the storage of variables I need between pages, but I use cookies to leave data on the user's computer in case they come back to my site and want to pick up where they left off. Both operations store variables, but are for different purposes.