I have just started testing out APO and it seems very promising. But I do have a few issues and questions.
I am guessing APO bypasses the cache for query strings, the natural thing to do. Facebook traffic often comes with a query string and parameters (fbclid), as Google News and other types of traffic (utm, gclid). I opened a CloudFlare support ticket about this a while ago (https://bit.ly/3ixgKuG).
Since I get a ton of traffic with query strings, I need to cache these requests, so I deployed a Worker that detects and caches those specific query strings. Unfortunately, it seems like the Worker is being bypassed by APO since requests made with fbclid and other query strings are returning cf-cache-status: DYNAMIC. Removing the query string from the URL returns cf-cache-status: HIT.
Is there any way to customize query string caching with APO? If not, I think this would be a very useful feature to have.
Can Workers work together with APO? If not, this would also be very useful.
Is there anything that can be done to get those query strings cached while using APO? I don’t want to use a Page Rule with a 301 redirect (that was the point of using a Worker).