Custom Made Firewall rule not working

[ngkarsten]

Cloudflare’s Scrape Shield still does not support customizing extensions to be blocked / does not support webp, webm, mp4, etc.

So I’ve looked it up and found this post: https://community.cloudflare.com/t/its-2021-why-does-scrapeshield-not-support-webp-yet/236841

I followed the instructions in reply by user erictung but it does not seem to work:

(http.request.uri.path contains ".webp" and not http.referer contains "example.org") or (http.request.uri.path contains ".webp" and http.referer ne "")

Where my actual website is located at b.example.org (the site that would use the file)

I tried including my website with the following:

(http.request.uri.path contains ".webm" and not http.referer contains "example.org" and not http.referer contains "example.org") or (http.request.uri.path contains ".webm" and http.referer ne "")

But it still does not work and block legit visits I made through different browsers. I realize I must be doing something wrong, what should I change in these rules or just let these slip and use only scrape shield?

[ngkarsten]

Solved this on my own, I don’t know whether it will be working but it seems working for me.

(http.request.uri.path contains ".webp" and not http.referer contains "example.org") or (http.request.uri.path contains ".webm" and not http.referer contains "example.org") or (http.request.uri.path contains ".mp4" and not http.referer contains "example.org")

will suffice for hotlink protection on Cloudflare’s side. The part http.request.uri.path contains ".webm" and http.referer ne "" is actualy unnecessary.