Workers enabled on domain & subdomain

Hi @vermaakpetrus,
Yes you can enable worker on the main domain and the sub domain separately. But I would suggest you not to use the worker mode as now better options are available with the latest version of the plugin by taking advantage of the Cloudflare Cache Rules. Check: https://gist.github.com/isaumya/af10e4855ac83156cc210b7148135fa2

This will give you a better result than worker and also free.

WOW! This is really awesome. I need to create those rules myself right? Or does the plugin manage it?

I think I’ve got it. How do I add if I have domain (example.com) and subdoman (sub.example.com).

Do I create separate rules for each or do I just add http.host eq “example.com”

Also, I do not have this option on the free plan:
Ignore query string order.

I have:
Cache by device type
Cache deception armor
Ignore query string
Enable query string sort

Can I ignore it?

I need to create those rules myself right? Or does the plugin manage it?

The cache rules needs to be created by yourself inside your CF dashboard.

I think I’ve got it. How do I add if I have domain (example.com) and subdoman (sub.example.com).

Do I create separate rules for each or do I just add http.host eq “example.com”

you can change http.host eq "example.com" with (http.host eq "example.com" or http.host eq "sub.example.com"). Or if your website just have the main domain and that one subdomain and no other subdomain, then you can remove that entire hostname check section.

Also, I do not have this option on the free plan:
Ignore query string order.

I have:
Cache by device type
Cache deception armor
Ignore query string
Enable query string sort

Can I ignore it?

In Rule 4, enable Cache deception armor and Ignore query string. Also if you are not using plugins like Easy Digital Download which requires the query string order not to be changed, then you can also enable the Enable query string sort. No need to enable Cache by device type.

Perfect! Thanks for the great support!

Will wildcart also work? Example:
http.host eq “*example.com”

Hi @vermaakpetrus,
No, you cannot use regular expression like * butif you are considering to use * then you can simply remove the hostname check from the rule which will then run for the entire domain (both the main and the sub domains).

Got it, thanks for the help!