[Koha-bugs] [Bug 11369] Too many search cursor cookies overflow HTTP-header size, when making multiple searches in the staff client.

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11369

--- Comment #26 from David Cook <dcook at prosentient.com.au> ---
(In reply to Katrin Fischer from comment #22)
> This works as described, at least if I haven't missed something.
> 
> Like some of the other commenters I would feel a bit better about this if we
> were not losing history here at some point by limiting the number of
> cookies, but stored the data in another place - sessions or using the HTML5
> feature.

I think using sessions is really the way to go.

I'm going to backport this patch to our local Koha, but I still think it's less
than ideal.

I think the best way to do this is to keep using unique IDs for the search, and
to store them and the relevant data in the active session in the database. 

In this way, we can still have multiple tabs open with unique searches and
still use the record browser without the limits imposed by using cookies.

At the moment, we store the OPAC record browser info in the active session in
the database, but the limitation is that the key isn't unique (ie the key is
"busc"). That means if you have multiple tabs open, the browser for all of them
will return the results for the latest search... definitely not a good thing!

-- 
You are receiving this mail because:
You are watching all bug changes.