digitalpoint
Well-known member
It hasn’t used Page Rules in a very long time (since about a week after the replacements like Cache Rules were introduced).
![[DigitalPoint] App for Cloudflare®](/community/data/resource_icons/8/8750.jpg?1692633961){kind=icon}
[DigitalPoint] App for Cloudflare® 1.8.5
- Thread starter digitalpoint
- Start date
Old Nick
Well-known member
Hi, what is the syntax to block an IP address range? I would like to create the firewall rule from the XF ACP. To replicate the rules in the message below. (i tried bu unsuccessfully) Thanks !
They are all from Singapore, and no valid traffic to any sites I host is from there.
I just blocked these 3 IP ranges:
They are all from Singapore, and no valid traffic to any sites I host is from there.
Mouth
Well-known member
digitalpoint
Well-known member
digitalpoint updated [DigitalPoint] App for Cloudflare® with a new update entry:
Ability to block AI crawlers/scrapers
Read the rest of this update entry...
Ability to block AI crawlers/scrapers
Read the rest of this update entry...
Chromaniac
Well-known member
So... About this:
Cloudflare now has a single toggle option related to this. But I am guessing you are creating a custom rule blocking specific user-agents and IPs? (I should probably just upgrade and check lol).
Alright. So it uses Cloudflare's own database of Verified AI Bots and Crawlers. I imagine it can be ignored if one has enabled their toggle to block AI crawlers. I wonder if Cloudflare makes this database public. Looks like it does here.
Cloudflare now has a single toggle option related to this. But I am guessing you are creating a custom rule blocking specific user-agents and IPs? (I should probably just upgrade and check lol).
Alright. So it uses Cloudflare's own database of Verified AI Bots and Crawlers. I imagine it can be ignored if one has enabled their toggle to block AI crawlers. I wonder if Cloudflare makes this database public. Looks like it does here.
Last edited:
digitalpoint
Well-known member
Internally it does it the same way as Cloudflare's toggle. The toggle in their dashboard isn't really a toggle, instead it's actually creating a custom firewall rule. If you edit the expression of that created firewall rule, the toggle will show as off, if you manually create a firewall rule with the right expression, the toggle will show as on even if you never toggled it on.
It's a bit weird from a UI standpoint in their dashboard since it's not actually a toggle, rather it's creating a firewall rule if you enable it and the toggle status simply reads all your existing firewall rules to see if one matches the expression needed.
Chromaniac
Well-known member
that's one way to consume user's allocated firewall rules 
digitalpoint
Well-known member
I'm not necessarily opposed to that, it is a firewall rule after all, and there's nothing preventing someone from combining it with another block rule by editing the expression with an AND if they need to save rules.that's one way to consume user's allocated firewall rules
I just think the toggle itself is dumb since it's not actually a toggle.
Mouth
Well-known member
Code:
Upgrading App for Cloudflare® from 1.8.4.1 to 1.8.5...
Confirm upgrade? (y/n)y
Upgrading
Complete.
Importing add-on data
Importing... Add-on data (Admin navigation)
Importing... Add-on data (Admin permission)
Importing... Add-on data (Class extensions)
Importing... Add-on data (Code event listeners)
Importing... Add-on data (Content type fields)
Importing... Add-on data (Options)
Importing... Add-on data (Option groups)
Importing... Add-on data (Phrases)
Importing... Add-on data (Routes)
In Parser.php line 832:
[ErrorException]
[E_WARNING] Undefined variable $yyact
Exception trace:
at src/XF/Template/Compiler/Parser.php:832
[...]
Running clean up tasks...
In Parser.php line 832:
[ErrorException]
[E_WARNING] Undefined variable $yyact
Exception trace:
at src/XF/Template/Compiler/Parser.php:832Running the upgrade a 2nd time, and it worked without error
Chromaniac
Well-known member
I got an error related to yyact thingy few days ago when upgrading to the latest rc. not sure if this addon has any connection to the issue.
So, it did manage to install the update completely after switching to CLI and back. Posting this here for reference for devs. Should have kept a text copy.
digitalpoint
Well-known member
Not sure... haven't seen it myself, but (probably) more importantly, the string yyact doesn't exist in this addon (only seeing it in XenForo's default Parser class). Could probably debug whatever it is in XF core if it was something I could actually reproduce, but haven't been able to yet.Code:Upgrading App for Cloudflare® from 1.8.4.1 to 1.8.5... Confirm upgrade? (y/n)y Upgrading Complete. Importing add-on data Importing... Add-on data (Admin navigation) Importing... Add-on data (Admin permission) Importing... Add-on data (Class extensions) Importing... Add-on data (Code event listeners) Importing... Add-on data (Content type fields) Importing... Add-on data (Options) Importing... Add-on data (Option groups) Importing... Add-on data (Phrases) Importing... Add-on data (Routes) In Parser.php line 832: [ErrorException] [E_WARNING] Undefined variable $yyact Exception trace: at src/XF/Template/Compiler/Parser.php:832 [...] Running clean up tasks... In Parser.php line 832: [ErrorException] [E_WARNING] Undefined variable $yyact Exception trace: at src/XF/Template/Compiler/Parser.php:832
Running the upgrade a 2nd time, and it worked without error
Maybe the parser is trying to parse something malformed possibly (even if that were the case, it should probably fail gracefully though).
