CloseSecureChannel not preceded by CloseSession when disconnecting from within onSessionInactive #1405
Replies: 4 comments 8 replies
-
This is intentional. If This means either:
In either case there's no CloseSession call attempted because either you don't have a Session to close or you just lost your connection and it will fail. |
Beta Was this translation helpful? Give feedback.
-
OK, I see. Thank you for your quick reply! In my case, it happens that the server doesn't respond to Keep Alive requests in time although the session is not closed and the connection is not lost. Of course the solution would be to adapt the Keep Alive timeout or to improve the server's response time, but I wonder if it would be possible and harmless to send a CloseSession request "just in case" ? |
Beta Was this translation helpful? Give feedback.
-
@FSangouard I'm tracking this in #1413 now, but I've kind of just convinced myself it's not necessary again. Quoting myself from that ticket:
I think this won't really be an issue any more in 1.0. It would be really helpful if you could try it out and confirm that somehow... |
Beta Was this translation helpful? Give feedback.
-
Hello again, congrats on the release of v1.0.0 ! I haven't had time to run any tests yet, I would like to give it a go but with all the changes introduced in 1.0.0, I was just wondering if there were any instructions, tips or caveats to upgrade from 0.6.x ? For example it seems there is no longer a |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am seeing a strange behaviour on v0.6.8 and I hope you can help me understand it.
When I call
disconnect
on a client, I usually see a CloseSession request and then a CloseSecureChannel request go through the network.But when I call
disconnect
on a client from withinonSessionInactive
, I don't see the CloseSession request on the network, only a CloseSecureChannel request.On the server side, when that happens they tell me the session isn't closed and just expires after some time, which seems to confirm the absence of a CloseSession request.
I tried to look at the code to understand why that is, but I can't figure it out. To me it looks like the session should be closed in every case.
Is that expected behaviour?
Beta Was this translation helpful? Give feedback.
All reactions