I can confirm that this is caused by ordering of options, ssl-sessions-use-cache seems to have effect only if cache is created before this option. Once I moved cache2 and ssl-sessions-use-cache before https2 option session IDs are used instead of tickets.
2014-03-31 17:28 GMT+02:00 Łukasz Mierzwa <[email protected]>: > I'm pretty sure I've set cache after https, so it might be the case, I'll > recheck later today. > > > 2014-03-31 17:22 GMT+02:00 Roberto De Ioris <[email protected]>: > > >> > I have enabled --ssl-sessions-use-cache but all tools I've used for >> > testing >> > showed that only tickets are supported, not session IDs. Maybe it >> requires >> > some specific openssl version for IDs to work? >> >> >> be sure cache2 options are specified before https2/https. Ordering is >> important (and unfortunately this issue cannot be easy addressed without >> changing lot of internals) >> >> >> -- >> Roberto De Ioris >> http://unbit.it >> _______________________________________________ >> uWSGI mailing list >> [email protected] >> http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >> > > > > -- > Łukasz Mierzwa > -- Łukasz Mierzwa
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
