Optimizely cache control issues on Safari?
We noticed one of our Analytics tools (Mixpanel) is firing events generated from long-archived Optimizely tests. The only way this could happen is if they were running ancient copies of our optimizely test js.
This is happening almost completely on instances of Safari and mobile Safari. I see issues on StackOverflow about cache control headers and Safari: http://stackoverflow.com/questions/9176874/webkit-not-caching-when-both-max-age-and-last-modified-he...
Have you seen instances of browsers caching optimizely test js well beyond its max-age?
I have never seen anything like this before with Optimizely so am not in the best place to help.
This an interesting one indeed.
As David recommend, I'd advise you (if you have not done so already) to send this over to the main support queue at email@example.com so that we can look into this further as it's hard to diagnose the problem based on this information alone.
Ideally, we'd like:
- a detailed description of the issue
- screenshots of this happening if available
- steps to reproduce the issue ourselves
- access rights if these are needed
Myself or one of our support staff will be happy to take a closer look into this and find out what the root cause might be.