It's not possible to set the following header with the current plugin logic:
cache-control: private, max-age=0, no-cache, no-store
as described here: https://mixmax.com/blog/chrome-back-button-cache-no-store
The fix would be relatively simple.
I could even submit a PR but I wanted to check if this would somehow violate a standard which this plugin implements? Or that's not the case?