Hi Nick, After setting api-session-timeout, I restarted Guacamole server.
>>it is possible that Chrome is hiding the actual window while still beginning >>to load parts of the page or keep the session active with the server I have recording enabled on session. But during site block, there is no recording file. So no parts of page have been loaded during block As soon as I allow block, Guacamole window pops up, and recording file appears and starts appending with data. Maybe block happens before guacamole starts processing, hence no timeout? Kind Regards, Adrian Owen | CTO | ForestSafe SessionSafe LAPSafe | PPM PAM | EESM From: Nick Couchman [mailto:[email protected]] Sent: 13 October 2020 11:42 To: [email protected] Subject: Re: api-session-timeout chrome block issue On Mon, Oct 12, 2020 at 10:56 AM Adrian Owen <[email protected]<mailto:[email protected]>> wrote: Hi Nick, What do you mean "blocked by Chrome"? I use JSON Auth API, and my Web application send JSON and receives AuthToken, Next I open the Guacamole URL+AuthToken in new browser window. But first time on Chrome, the popup blocker, blocks the guacamole window. In that case, whether or not the API timeout is effective is going to depend upon whether there is any other traffic that would keep that session alive. I do not know the internals of how Chrome's popup blocker works, but it is possible that Chrome is hiding the actual window while still beginning to load parts of the page or keep the session active with the server on the chance that you'll want to allow the pop-up and continue. Again, I don't know this for sure, it's just my speculation on what might be going on - you'll have to investigate further in Chrome. Also, when you changed the API session timeout property in guacamole.properties, did you reload the web application (restart Tomcat or re-deploy Guacamole)? -Nick
