I have a haunted server.
Let me give you the scenario. I have a program written in CherryPy
that we use on our local network to schedule patient transportation.
The server was running Fedora 4 and CP 2.3. This week I upgraded the
server to Fedora 9 and CherryPy 3.0.3. I had already ported the
application to 3.0 on my development box.
If you use the application via Internet Explorer, it creates a new
session id with every request. If you use Firefox it doesn't.
I didn't want to take the server offline, so I grabbed a spare PC
thinking I would duplicate the condition on a test "server" while I
tracked down the problem. I used the same Fedora 9 DVD and the same
code, literally extracting the same tar file from a flash drive -- and
it worked fine in IE.
Consider this snippet:
@cherrypy.expose
def show_id(self):
return str(cherrypy.session.id)
http://192.168.10.12:8080/show_id <-- live server, NEW session id each
refresh
http://192.168.10.14:8080/show_id <-- test server, SAME session id
each refresh
Same code, same os, same libraries, same client machine & browser
doing the testing. The only differences are the hardware; Dell server
vs. an HP desktop, and the live server runs on the same box as the
PostgreSQL database but I'm using file based sessions.
Lastly, sessions used to work just fine on this box before the big
update.
Any insights would be greatly appreciated.
Regards,
Jim Storch
