header already sent problems about php-auth HOT 3 CLOSED

I can confirm that I've had this issue (or one very similar). Unfortunately I don't have a test case, but my workaround was using \Delight\Cookie\Cookie::setcookie instead of $_SESSION

from php-auth.

SOLVED.... Trailing blanks before the <?php header('Location were the issue...

from php-auth.

@rgvy Thanks for helping! That code change was probably only part of the workaround, or something else caused the problem to go away :)

@PatrickCaneloDigital Thanks for resolving the issue and for explaining what caused the problem in this specific case.

In general, the "headers already sent" error occurs whenever some output has been written to the response body and you still try to set or modify HTTP headers after that. This does not work, because as soon as you write text or binary data to the output, the server may send the HTTP headers (which go before the output) to the client. Often, this happens because you have accidentally written some whitespace to the output, as in this case.

from php-auth.