Exclude js string + Private Cache TTL

1. yes , but please add both pdf and PDF
2. sadly not at this moment , when you use private cache , the disk usage will increase exponentially , so we limit it to a relative lower time , let’s say your site has 1000 visitor , if they are all guest user, then 1 cache copy ought do it , but if there are 1000 login users , then you will need to have 1001 cache copies , the disk space usage increased thousandfold
3. most likely the private cache generated by A , will not be shared with B even same account, the private cache is linked with multiple factors , like user IP , cookie value …etc

the issue from your 1) is not about private cache , the issue is the javascript

from what I see in error message , I imagine this

the PDF plugin has a js file , let’s say my-pdf.js , it will look for (file-name).worker.js ideally , it to be my-pdf.worker.js

but as you have enabled option like JS minify or JS combine , the original file name is changed, to something , just imgine here , /wp-content/litespeed/js/abcdefghijklmn.js , so it now looks for abcdefghijklmn.worker.js and it will end up 404 error

so in theory , exclude that PDF’s js from being JS optimized , should fix for you.

1. Thank you for your explanation! I have followed your instructions.

2. Private cache TTL. We have 75 students and not that many pages to be cached for private cache. They spend 2 a 4 hours on our website. At least 4 hours TTL would be a big improvement. Maybe you can add a warning (+ size of the private cache) to the setting, so admins will be made “aware” of what they are doing?

PS: Is it a problem (below)?

[18-Jul-2023 09:50:00 UTC] PHP Deprecated: Creation of dynamic property LiteSpeed\Lib\HTML_MIN::$_html is deprecated in /httpdocs/wp-content/plugins/litespeed-cache/lib/html-min.cls.php on line 70

hm , no , not a problem , it’s a deprecation warning , means something will no longer work in future version but still works for now

for cache login users, you could try go to Cache -> ESI -> enable ESI , this will generate public cache among same role users and use ESI to privatize cache for certain section , but it may not be compatible with your theme or plugin , but you can give it a try.