Hi!

> Note for this issue.
> The change does not breaks normal codes as PHP cannot set new session
> ID when header is already sent. The session is _not_ accessible
> anyway. Not writing orphaned session does not matter at all.

So it looks like this particular breakage is because write does not
happen when cookies could not be sent. However, it is not necessarily
true that session is not accessible in this case - session ID can be
passed by other means, not only via cookies, and it also may be existing
session ID. The second part of this test opens session with known ID,
but write still does not happen.
I think assuming that if cookie sending failed then the whole session
failed is dangerous. Also, removing session write is a pretty serious
change, I'm not sure this should be happening in a stable version.

> If you understand exactly what is happening, it is understandable this
> is not a BC for production code, but only breaks test code that
> inspect session behaviors and it found out bogus write() is gone now.>
> Anyway, to fix existing app/framework unit test failures, (it's not
> fixing anything but leave bogus write(), though)
> removing php_session_abort() from php_session_cache_limitter() should be 
> enough.

Yes, this patch: https://gist.github.com/smalyshev/4d8435b7993bef80c0ed
fixes it for me. Remi, could you check that it also fixes the failures
in the test suites?

-- 
Stas Malyshev
smalys...@gmail.com

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to