RE: [PHP] FW: Cookies, Dammit!

In this case, the value of the cookie is pulled from a database; the specific value depends on the URL at the user is redirecting from. If the user comes from www.domain.com/minisite1/index.htm then when they're directed to www.domain.com/index.htm, they should see "Welcome from minisite1"; but if they come from www.domain.com/minisite2/index.htm they should see "Welcome from minisite2" when they're redirected to www.domain.com/index.htm. it's a bit more complicated than that, but that's the general idea. Hope that helps. -- Richard S. Crawford Senior Web Developer NeuroHub, Inc. (916)789-4167 / (530)307-0069(cell) AIM Handle: Buffalo2K http://www.neurohub.net -----Original Message----- From: Jason Brooke [mailto:jason@qgl.org] Sent: Tuesday, January 16, 2001 2:48 PM To: php-general@lists.php.net Subject: Re: [PHP] FW: Cookies, Dammit! The thing that usually intrigues me is why people design their application so that it needs to redirect to another page just so that they can attempt to read the cookie back. Do they not already have the value of the cookie in order to be able to set it? Why attempt to read it back straight away? jason > Some browsers just can't handle a redirect and a set-cookie header in the > same request. How you get PHP to generate these headers is irrelevant. > > -Rasmus -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net For additional commands, e-mail: php-general-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net