On Tue, 19 Jul 2016, Sebastian Benoit wrote: > maybe session cache disable should disable tickets too.
Well, what problem are you trying to solve by offering that option? If it's to save memory, because original-flavor session caching requires state and overhead on the server, then you should only disable it and not tickets. If it's because this relayed is for handling some resource which is SO SPECIAL that you want fresh proof of liveness for every new connection and thus totally disable session reuse, then sure, disable tickets too. Which is the real case? Maybe you should throw in some stats tracking too see how often the different flavors of caching are used in your real-world use. Maybe original-flavor session caching should be disabled because no one real is using it and it's just more exposure to leave on... Philip
