Re: [PHP-DB] Cookie effect

2001-05-12 Thread Jason Brooke
> David > > > problem is, the cookie only comes into effect after I've clicked thru to > > another page from login.php...any ideas on this? Sure - it's because of the way the http protocol works. If you've just set a value in a cookie, why do you need to read the cookie back in order to check the

Re: [PHP-DB] Cookie effect

2001-05-12 Thread Geoff Caplan
David > problem is, the cookie only comes into effect after I've clicked thru to > another page from login.php...any ideas on this? You don't explain why you need to access the cookie immediately. If you just want to check it has been accepted, the usual approach is to use headers to do a redir

Re: [PHP-DB] Cookie effect

2001-05-11 Thread Jesse Scott
I believe that this is the default and only possible behavior. The browser won't return the cookie value until another page is loaded. But since you set the cookie on that page, you should still have access to the variables you used to set the cookie right? From the manual: "Cookies will n

Re: [PHP-DB] Cookie effect

2001-05-11 Thread Ashley M. Kirchner
On Fri, 11 May 2001, David Balatero wrote: > I have a login script that sets a cookie on your hard drive...the only > problem is, the cookie only comes into effect after I've clicked thru to > another page from login.php...any ideas on this? My (abridged) code is > currently: > > header("Set-Coo