error in mysql/php

abda53

ive been getting this...

Warning: Cannot add header information - headers already sent by (output started at /user/index.php3:2) in /prep.php3 on line 170

            function loginCookie($uid, $pwd)
            {
GLOBAL $geeklogin;
$geeklogin = rawurlencode($uid . ":" . $pwd);

line 170 setcookie("geeklogin", $geeklogin, 0, "/");
}

im not sure what the index.php3:2 means..

anyone got any suggestions?

MrAlaska

'Line 170' does not belong there, but if that was in your actual code you would be getting a parse error so I assume that slipped into the editting.

'Headers already sent' is a common error. The first time I encountered it I did a google search which wasn't much help because it found hundreds of sites who were actually displaying that error. A search on the topics of a site like this using the key expression "headers already sent" will yield more fruitful results, several of which answer your question.

You get that error by trying to print something out before you send the header information (a cookie, in this case) Since your cookie is in a function, you need to make sure you are not printing anything out before you call the function.

Another common thing that will generate that warning in some cases is to have white space on your page before the first <?php tag in your code or after the final closing tag ?>

abda53

yup thanks.. i just put the line in there to show what the line it was that was being referenced..

i checked on google earlier and saw the same thing you did.. and also read up from other places what your talking about.. im just kinda unsure on which page this applies to.. because theres only one page that you log into.. but even when i moved it to the top of the actual login page, i was showing the same error.. but i dunno.. i play with it some more..

MrAlaska

Since it is a function that is setting the cookie, it does not matter where you put that code. What you need to look for is anything printed out before you CALL the function. When they post from the login page, the cookie function needs to called as soon as the verification happens and before anything is echoed to the user.

The general inadvisability of putting the user variables in the cookie instead of storing them locally and generating a unique ID to put into the cookie is another topic of discussion, so I won't mention that.