Revision history  [back]

I think this is related to session - if you choose cached session engine and have cache like memcached or redis you should not have this issue.

The search state is currently stored in the session and if session ends up being stored in the process memory space you may end up with several sessions per user.

We are now reworking the search function so that it does not depend on the session.

It is definitely not related with the page caching or setting of ignored or interesting tags.