APO - fbclid query string not being cached properly, returns cf-cache-status: MISS


A few months ago, the APO team (including @yevgen) implemented a fix to enable caching of query strings, like fbclid and UTM. It was working great until recently.

Today, I discovered that all fbclid query strings with any parameters (?fbclid=xJDJDxXmxmbeEFDFw) are being cached individually and return cf-cache-status: MISS on a second pageview with different query string parameters. In reality, every request with ?fbclid, regardless of the parameters, should return the same cache entry.

For example:

https://www.example.com/?fbclid=xJDJDxXmxmbeEFDFw -> cf-cache-status: MISS
https://www.example.com/?fbclid=bvgVERERWFVVSDDS -> should be cf-cache-status: HIT even if the parameter is different, but also returns cf-cache-status: MISS.

I know this has been fixed before as I was the one who had opened a ticket (APO and Query String Cache). I’m not sure why it isn’t working anymore, but it is very important to have it working properly, especially for sites that receive lots of Facebook traffic (like mine).



it’s most certainly a regression because of APO: tiered caching testing. We will look into the issue ASAP.

1 Like

We will fix it in the next 4h, sorry for the problem with a bad release.


No problem @yevgen, it happens to the best of us.

Thanks for the quick reply & fix!

1 Like

Hi @yevgen, I was simply wondering if the issue had been resolved? Is there anything we need to do on our end to make it work once the fix is deployed?

Edit: I just noticed it’s been fixed and there’s nothing to do on our end. Thanks!

1 Like

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.