I had reached out to support last week but they were not very helpful. It seemed the person I was dealing with was not even aware of the feature. At this point I am still without a solution. Was hoping Jason (freakdesign) would have chimed in as he seems to be the one of the only places on the internet referencing it.
cache=false was never an officially documented property so using it was a bit of a hack. I've used it before in some old builds, and I've got a bunch of blog posts on the topic. However, being undocumented I also knew the lifetime was limited, and it could be removed at any point. Opting to not return cache has performance concerns for everyone.
If you're using a querystring to determine what collection to show (since that's the most recent post in this thread) that sounds like something you could achieve with JS.
If you have absolute must have use cases I'd be interested to know what they are.
Experiencing the same issue. :( If you open the request in new window/tab then it will provide you fresh content whereas in ajax request cached content is loaded. Any work around for this one? We have lots of things which are dependent on this one in our store.
Shopify should provide alternate method for this one. :)
I have a case where I am using this :
to create a facebook xml feed.
When Facebook scrapes the output it never gets the latest version and caches it's first response. I presume this is the Shopify cache working in the network between Facebook and Shopify (Cloudflare?).
How to best signal that this page shouldn't be cached? I'm currently testing using cache=false
|an hour ago|
|an hour ago|
|2 hours ago|
|4 hours ago|