Suggestion: Make cache-no headers optional
The plugin adds in this code to force no-cache:
header('Cache-Control: no-store, no-cache, must-revalidate');
Now I cannot say this is incorrect, however I have a (probably one off) situation where I both want https AND caching. I know. How crazy is that?
It would be nice if there was an option, or even a secret define, that could be used to say “But leave my cache-control alone please and thank you”
Right now we’re forcing the matter with nginx, and that MAY be the best solution in the long run, but I thought there’s no harm in asking 😀
- The topic ‘Suggestion: Make cache-no headers optional’ is closed to new replies.