Question

Weblink 9 Returns blank results with aggressive session timeouts. Mysterious &cr=1 appears in URL

WebLink

Updated October 26, 2015

asked on July 6, 2015 • Show version history

Hi there,

Background:

We are public facing Weblink 9 for our citizens. That being said, in order to prevent licensing issues, we are aggressively timing out sessions per Laserfiche's advice.

Issue:

Initial search on a Weblink page works great. But if the page is left alone for a while and the user attempts another search, the results are blank. The URL on the blank results also now has a bonus string of &cr=1 appended to it. It is this &cr=1 that appears to be the root cause. This &cr=1 only shows up after the session times out. If I do queries before the timeout, results are great.

The question is why is this happening? Why is &cr=1 causing issues and creating blank results?

We are not running Weblink on any unique ports or anything like that, so the port redirect issue in a recent KB does not apply.

I suspect the cookie checking engine is having issues?

0 0

Replies

replied on July 10, 2015

Hello Eric,

We looked into your issue about auto-reconnecting after a timeout and found that although most buttons and links do successfully auto-reconnect you, searching does not. This is because searching relies on cookies which are cleared when you get your authorization cookies back upon logging back in. If your connection times out, you won't be able to run a search as the 'first click back', but it will work if you run it again. It will also work if you click something else to log you back in and then run the search.

We will look into better handling for this in future releases.

1 0

replied on July 13, 2015

Thanks Jared, glad I was not losing my mind over here. As a side note this issue is compounded when you use target="_blank" in the search form. We do this because we <iframe> a weblink search form on the main website so it looks seamless. The target="_blank" then sends them to the main weblink site via a new browser page/tab with the results. So in short, more opportunity for that initial session to be forgotten about and time out.

Thanks for your time. I'm confident you folks will have this sorted out down the road.

Regards

0 0

replied on July 7, 2015

Hi Eric,
Sorry for my english, but try to be successful with my translation.
If I understand your question correctly this is on a topic in the IIS session - Session State feature, which defaults to the output time parameter is 20 minutes, now it means; the public user has been authenticated to Laserfiche persist connection with no activity for 20 minutes after this time will be disconnected automatically, this will be checked by entering administrator Laserfiche and active sessions will see the user disconnects automatically, if It is necessary for the user to remain active for a longer search time increases from the state of sessions in the IIS.
----

Hola Eric,
Disculpa por mi inglés, pero trataré de ser acertado con mi traducción.
Si he comprendido correctamente tu consulta esta va por un tema de sesión en el IIS - Session State feature, el cual por defecto en el parámetro de tiempo de salida es de 20 minutos, ahora que significa esto; que el usuario público con que se ha autenticado al Laserfiche persistirá su conexión sin actividad por 20 minutos transcurrido este tiempo será desconectado automáticamente, esto lo podrá comprobar ingresando al administrador del laserfiche y en sesiones activas verás que el usuario se desconecta en forma automática, si es necesario que el usuario se mantenga activo para la búsqueda un mayor tiempo aumenta el tiempo de salida en el estado de sesiones en el IIS.
Saludos.

0 0

replied on July 7, 2015 • Show version history

Hi Manuel,

Yes, Session State is involved here but probably not the main issue. I suspect the main issue here is Weblink 9's new cookie tracking feature. I think searches are getting redirected to some cookie tracker .aspx page first and then redirected to the search results. This process appears to break when session state times out and is reset by IIS. When this happens, the cookie .aspx page writes a &cr=1 to the end of the query string in the URL and completely fouls everything up resulting in empty search results.

All suspicion of course. I'm not exactly sure how the whole weblink 9 wheel is turning. All I know is &cr=1 appears to be the devil.

0 0

replied on October 26, 2015 • Show version history

I had the same problem with weblink release 9, download again the installer and reinstall weblink, the problem was solved.

Regards.

0 0

You are not allowed to follow up in this post.

Question

Question

Weblink 9 Returns blank results with aggressive session timeouts. Mysterious &cr=1 appears in URL

Replies

Sign in to reply to this post.