Wt

Korneel Dumon wrote in #note-1:

Hey,
I looked into it a little bit. When you close the browser, the session is cleaned up after 5 seconds when using reload-is-new-session. We really expect a reload, not a 'come back after a few hours'. So I don't think it affects this.

Do you have any more info to make this reproducible?

I had it two different projects. One of them is a small one. But the only information I have is, that it works as expected with fcgi. But when I run the same application with the built-in http through an reverse proxy (Apache2), I need to reload for the page is working. And even that I use the Auth widget, it isn't just the Auth fucntionality which isn't working. No events are working then.

I would actually assume that if you close the browser and go back later, you are already refreshing somehow. Or do you think this is somehow not happening? Even when I let the browser restore my tabs, it always seems to refresh them.

If events are happening for a session that the server has already removed, I can imagine that you get the behavior you describe. The server would simply ignore those events.

Korneel Dumon wrote in #note-3:

I would actually assume that if you close the browser and go back later, you are already refreshing somehow. Or do you think this is somehow not happening? Even when I let the browser restore my tabs, it always seems to refresh them.

If events are happening for a session that the server has already removed, I can imagine that you get the behavior you describe. The server would simply ignore those events.

I don't know why it happens. But I found out that it is a difference between using fcgi or built-in server. Which the built-in-server it is like described, but when I use fcgi, then everything is fine. Then I don't need to do a reload.