Vagharshak Tozalakyan - 2008-08-25 15:21:19 - In reply to message 1 from damian
I don't know how your script is oranized that's why I can't say anything exactly. Anyway, as an option you may call session_regenerate_id() separetely and turn off $regenerate_id in
your SecureSession object.
Henrik Hansen - 2008-09-22 08:17:41 - In reply to message 1 from damian
I had the same problem in my code to begin with. I had the same error, but only in some php files on my site. Very wierd.
I require() the auth.php in the very top of every one of my php files, but still I got an error, that headers was already sent. I searched for spaces and breaks, but nothing, everything seemed fine.
Then, by looking at the error text in the resulting HTML, I could see, that the error text appeared after the meta tags in the html code. Hmm. How the *** does this happen, when I require() the auth.php in the top? I still don't know, but I had an include() or require() some lines below in the php code and that is obviously too much to handle for php. It is probably also bad programming, but schhht! :) So I moved all my require's and include's to the top of my php files and the error disappeared.
Vagharshak Tozalakyan - 2008-09-22 16:33:09 - In reply to message 7 from Henrik Hansen
"Headers already sent" error appears when any kind of output was sent before starting a session. It could be headers, markup, spaces, line breaks or just invisible symbols (e.g. in the top of Unicode files). I can suggest to use a hex editor for scanning the output. Also, you may use telnet to see the complete HTTP request.