I am having trouble configuring Cloudflare worker to extract referrer details
What are the steps to reproduce the issue?
I’m exploring Cloudflare’s O2O (Origin-to-Origin) feature and its potential benefits for a Shopify store. I’d like to understand how O2O works when Shopify is already integrated with Cloudflare.Specifically, I’d like to know:
Use Cases - How can Cloudflare Workers be used in conjunction with O2O to extract referrer details and pass them to Shopify for analytics or tracking?
Prerequisites - Are there any specific requirements or configurations needed on Shopify’s end to enable Cloudflare O2O?
Limitations - Are there any known constraints or compatibility issues with Shopify’s infrastructure when using O2O?
Without O2O, requests go directly to Shopify and do not pass through your Cloudflare account so Cloudflare’s analytics will be blank in your account and any rules, workers or other features won’t do anything.
You shouldn’t need to extract referer details, they will be passed through in the headers of the request anyway for Shopify to handle however they do that. But with O2O, that information will also be in your account analytics and if you want to put a worker (or WAF, Redirect or other rules) in front to do stuff, then you can.
Nothing about O2O itself will cause downtime, but if you’ve already added rules or configurations in your Cloudflare account that are broken or buggy then these will cause problems once O2O is enabled as those are applied to the request pipeline. Just disable the proxy to quickly return to working while you fix those.
Will this work with other apps that use their own proxy? For example, if I have App X with its own proxy, would having multiple proxies cause any issues?