Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cache-control header combination not possible #11

Open
jglapa opened this issue Jun 5, 2018 · 0 comments
Open

cache-control header combination not possible #11

jglapa opened this issue Jun 5, 2018 · 0 comments

Comments

@jglapa
Copy link

jglapa commented Jun 5, 2018

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant