[Yazlist] Pazpar2 session expires prematurely

[Sebastian Hammer]

Hi Chris,

You don't say how much time passes between these two requests. Sessions 
time out after 1 minute, a period which cannot be changed at the moment 
without altering the source code (it's on the todo list).

Our pazpar2-based applications generally either use the 'ping' command 
to keep sessions alive as long as needed, or they contain logic to 
restore the session (and repeat the query) if needed. In fact, we have 
developed a couple of 'pazpar2 proxies' which perform these functions, 
including dynamic target configuration based on who the user is, etc...  
whether one of these end up in the open source pool is to be determined.

--Sebastian

Christopher Morgan wrote:
> I've been querying my pazpar2 server directly via GET requests. First I
> obtain a session number using
> The init command. But when I issue a stat command containing that session
> number, I get this error message:: 
>
> pazpar2 [log] Request: GET /search.pz2?command=init
> pazpar2 [log] Request: GET /search.pz2?command=stat&session=16982625301
> pazpar2 [warn] HTTP 417 Session does not exist or it has expired:
> 16982625301
>
> 16982625301 is the session number I captured via the init command. Pazpar2
> works fine if I query it from my web page interface. I've been using Firebug
> (thanks for the tip, Sebastian!) to observe these successful sessions, but I
> don't see what's causing the problem. Am I leaving out a step?
>
> - Chris Morgan
>
>
> _______________________________________________
> Yazlist mailing list
> Yazlist at lists.indexdata.dk
> http://lists.indexdata.dk/cgi-bin/mailman/listinfo/yazlist
>
>   

-- 
Sebastian Hammer, Index Data
quinn at indexdata.com
www.indexdata.com