TLS session resumption problem
|Reported by:||Michael Roy||Owned by:|
|Component version:||Rumpus 8.2/Rumpus 9.0||Operating system type:|
|Operating system version:||Windows 10 and Mac OS 10.14.6|
Using Filezilla 3.53.1 and sessions cache limit with the new TLS session resumption seems to cause problems.
(In order for a session to be restored, a cache of previous sessions needs to be maintained. Essentially, these cached sessions are the stored sessions that can be resumed.) There is a limit of 255 sessions in the cache on our server, which means that not all past sessions are capable of being resumed. I think client should definitely not generate an error because a server does not have a previous session recorded in its cache.