Wordpress LScache Plugin: ESI Nonces second parameter and TTL
Last Updated on: Wed, 15 Apr 2026 00:00:02 Hi, We have recently encountered issues with nonces that were cached to long even though we had our nonces added to the list with the parameter private. Our rivate TTL is set to default value of 30 minutes. Litespeed describes that ESI blocks can be cached privately, cached publicly with its own TTL, or not cached at all . In the description under ESI Nonces field it says: optional second parameter may be used to specify cache control. Use a space to separate: my_nonce_action private My question is, how are the nonces cached if no parameter is specified? And are there other parameters than private that can be specified? I have searched but did not find any information on https://docs.litespeedtech.com/lscache/lscwp/cache/ Also, does it make any difference if a nonces is generated via shortcode? For example, a form plugin that allwos forms to be included on a page via a shortcode. The cache control parameters can be public or private along w/ no-vary(comma connector, e.g. public,no-vary) or any other valid cache control header if there is one. No difference as long as the nonce used WP func to generate. Nonce cache control is from https://github.com/litespeedtech/lscache_wp/blob/master/litespeed-cache.php#L130 then https://github.com/litespeedtech/lscache_wp/blob/072fd226ab226e07ff4a3e56751015a83f8915ce/src/esi.cls.php#L406 you can see by default if not specify, it is private,no-vary. Generally speaking, you can just simply check plugin debug log to see the answer of your question if you dont want to check PHP code to trace how ESI nonce is used in https://github.com/litespeedtech/lscache_wp/blob/master/src/esi.cls.php#L800 .
LiteCache Rush: Speed comes from using less, not from doing it faster
Reference