When using Siteground’s optimizer and enabling APO through it they appear to have some kind of bespoke implementation. It does enable the APO setting in cloudflare, but also creates a sg_worker in CF with what looks like custom code for edge caching.
Can anyone explain what’s happening here (because apparently SG support can’t.)
It is bespoke or does the official cloudflare plugin do the same thing (does it also add a worker for this?)
My reason for querying this that we have our own domain level routing worker which I don’t want overridden by the other domain level sg_worker. I’m wondering if the normal cloudflare version does not do this.