Hello,
A quick question:
If I recall correctly, it was possible to set the galaxy session cookie name with the "session_key" variable in "universe_wsgi.ini".
I'm not sure about that, but I think it was possible, because I'm running two instances (at least) from the same server, and I explicitly set the cookie names to by different.
Now it seems that the cookie is always "galaxysession" - was that changed recently, or am I missing something?
One reason that I ask: The "path" of the cookie is always hard-coded to "/" (probably in lib/galaxy/web/framework/__init__.py:set_cookie as the default parameter) - so when I run two galaxies from the same server (with different "prefix" filter) - they are now forced to share the same session cookie.
I think this is causing some history related problems in one of my servers: galaxy always thinks there is no active history selected. Example: 1. I click "list saved histories" 2. Select a history 3. The history pane is updated. 4. I click on "refresh" history 5. a new, "unnamed history" is created, without any datasets.
The log shows error like: alaxy.web.framework DEBUG 2010-04-04 23:48:39,512 Error: this request returned None from get_history(): http://rave.cshl.edu/devglx/history/list
Any ideas ?
Thanks, -gordon