Thread:Project:Support desk/v1.20.2 installation problem - cannot log in/reply (2)

I recorded the login with tcpdump and this is what I see. It all starts with a bunch of GETs interspersed with occasional "200 OK" or "304 Not modified" replies. Then I clearly see my POST with username/password, to which the server replies with "302 Found". In that reply there is some cookie information and a new PHP session id. This must be the cookie you mean. The answer to your second question is unclear because my browser sends PHPSESSID *twice* in the "Cookie:" line when it reGETs the page I clicked "Log in" on. At the beginning of the line it sets the old PHP session id, and at the very end of the list the new one. I have no idea why that is so, or which of the two assignments counts in the end.

Checking cookies in the browser (FireFox 16), I do see UserName and UserID set to the same values as in the server reply, and PHPSESSID is set twice. First for the domain, with the value the server sent after POST, then for the server itself, with a 3rd value that is different from the values that appear in the packets.

So... is there anything odd about the behavior described above?