Nothing Special   »   [go: up one dir, main page]

[DigitalPoint] App for Cloudflare®

[DigitalPoint] App for Cloudflare® 1.8.8

No permission to download
Yes. I’ve got a Singapore 🇸🇬 bot that lives on my board. Finally blocked the country, but he still gets through. It’s a Huawei data center location. Always viewing unknown page.
 
Thank you, I just discovered that I hadn't edited my robots.txt file, and it was configured with the /community/ path, which I don't use. :rolleyes:
 
I have a question, you might be able to help me. I've set the Cloudflare SSL/TLS to Full (strict) and site's URLs all redirect non-www to www. But for some reason URLs for attachments and .txt files etc. are flexible between www and non-www. For example:
Code:
https://www.joyfreak.com/data/avatars/o/0/2.jpg?1720952280
https://joyfreak.com/data/avatars/o/0/2.jpg?1720952280

What is going on here?
 
I don't think so. If you don't want a search engine to index certain things, just use robots.txt to tell them what you don't want indexed.
Ok but...
User-agent: *
Disallow: /whats-new/
Disallow: /account/
Disallow: /attachments/
Disallow: /goto/
Disallow: /posts/
Disallow: /login/
Disallow: /search/
Disallow: /data/
Disallow: /styles/
Disallow: /css.php
Disallow: /admin.php
Allow: /
And
Capture d'écran 2024-07-29 150314.webp
It doesn't seem to have any impact.
 
I recently added a 50reqs/10sec rate limiting rule to abate a fairly aggressive scraping bot originating from China that was causing high server load and normal usage lag/delays. This was much easier, and more effective, than playing 'whack-a-mole' with IP address blocking, when it was persisting from changing IP addresses.
What's the cost associated with that though? I understand CF charges for rate limiting.
 
Deleting Cache Rules in the addon page throws this error:
Code:
Client error: `DELETE https://api.cloudflare.com/client/v4/zones/7c8d4fc8153e104bad38abeb9e797c1e/rulesets/1089a421a79542b1a60258c3d79cea88/rules/0615f1ae4ac14274aab9aef14a51567a` resulted in a `400 Bad Request` response: { "result": null, "success": false, "errors": [ { "message": "invalid JSON: '' cannot be a array" } (truncated...) / {"result":null,"success":false,"errors":[{"message":"invalid JSON: '' cannot be a array"}],"messages":null}
 
Deleting Cache Rules in the addon page throws this error:
Code:
Client error: `DELETE https://api.cloudflare.com/client/v4/zones/7c8d4fc8153e104bad38abeb9e797c1e/rulesets/1089a421a79542b1a60258c3d79cea88/rules/0615f1ae4ac14274aab9aef14a51567a` resulted in a `400 Bad Request` response: { "result": null, "success": false, "errors": [ { "message": "invalid JSON: '' cannot be a array" } (truncated...) / {"result":null,"success":false,"errors":[{"message":"invalid JSON: '' cannot be a array"}],"messages":null}
Probably not a lot that can be done about a full rebuild being slow. There are 11 API calls being made (one for each stat that is logged). Most are run in parallel to speed it up, but let's say it takes 1 second to make the 11 API calls...

Realistically, it will probably be more than 1 second, but even if it was only 1 second, the API calls would cumulatively take more than 6 minutes per year of the rebuild.

The only solution would be to not make the API calls for each day of the rebuild (the easiest way to do that would be to disable the addon before a full rebuild). Certainly could do that automatically and never fetch stats for a full rebuild, but it seems like it probably makes sense to let people get the data if they want even if it's not lightning speed.

Deleting Cache Rules in the addon page throws this error:
Code:
Client error: `DELETE https://api.cloudflare.com/client/v4/zones/7c8d4fc8153e104bad38abeb9e797c1e/rulesets/1089a421a79542b1a60258c3d79cea88/rules/0615f1ae4ac14274aab9aef14a51567a` resulted in a `400 Bad Request` response: { "result": null, "success": false, "errors": [ { "message": "invalid JSON: '' cannot be a array" } (truncated...) / {"result":null,"success":false,"errors":[{"message":"invalid JSON: '' cannot be a array"}],"messages":null}
Ya, looks like they changed the API call for cache delete to not want anything in the JSON "body".

Fixed for the next version, but you can also do this if you want the fix now...

In the DigitalPoint\Cloudflare\Api\Cloudflare.php file, change this:

PHP:
return $this->makeRequest('DELETE', sprintf('zones/%s/rulesets/%s/rules/%s', $zoneId, $rulesetId, $identifier), ['json' => []]);

to this:

PHP:
return $this->makeRequest('DELETE', sprintf('zones/%s/rulesets/%s/rules/%s', $zoneId, $rulesetId, $identifier));
 
Back
Top Bottom