On Mon, 17 Oct 2011 18:14:42 -0500, Brion Vibber wrote:
On Mon, Oct 17, 2011 at 3:54 PM, Dan Nessett dnessett@yahoo.com wrote:
Well, I upgraded one of our small wikis to 1.16.5. I don't know yet whether it fixes the login session problem, but it seems to create another problem. Atom feeds appear broken in 1.16.5. MW is inserting an extraneous line feed into the response to the atom feed request.
This is usually because of extra whitespace in LocalSettings.php or a custom extension file that has been manually edited. Check all your .php files for stray whitespace at the beginning or after a closing ?>
-- brion
That was it, thanks.
Getting back to the original problem, I am attempting to develop a way to force the problem to occur, so I can test whether 1.16.5 fixes the problem. On a development machine and a development wiki running 1.16.2, I changed the following values in php.ini:
session.gc_maxlifetime = 60 session.gc_probability = 100 session.gc_divisor = 100
From what I have read, I thought this would fire up the session garbage
collector on each access and timeout sessions after 60 seconds. It appears the latter is true, since if I log in (not setting "remember me"), edit a page, wait 60 seconds and try once again to edit the page, the latter is disallowed and the resulting response shows me logged off.
However, when I look at the sessions directory, the session created by my login is still there. Maybe I don't understand what the garbage collector does, but I assumed it would destroy the session record if its lifetime exceeded maxlifetime.
I know this is a PHP question, not a MW question, but I was hoping someone might fill me in. By the way, I am running PHP 5.3.4.