Hello @zakri ,
This is a follow-up here, Yesterday I got a reply from Omar saying to enable image transformation you need to enable from Images>Transformations > then domain to enable. But to Disable you need to clear you URL from internet.
This brings me to my question: if a DDoS attacker obtains the URL and continues to send requests via proxies, wouldn’t this still result in charges, even if Images > Transformations is disabled? This seems like a loophole, as the system would still incur charges despite the requests not originating from us.
For context, we were using the Transform via URL feature:
https://<ZONE>/cdn-cgi/image/<OPTIONS>/<SOURCE-IMAGE>
Clearly, this setup requires the zone to be enabled. However, when disabled, it should no longer process requests.
Also we were using Worker for og image watermark, We disabled the Transformation via dashboard on 27th December and removed watermark and everything from codebase on 23rd January. To be noted that OG image get calls when a news is being shared. Could the Worker be responsible for the increased billing during that time?
Also, why the dashboard showed 196,172 Image Transformations from 19th Dec - 19th Jan but we got charges for 785,930 Transformation, Which figure is accurate? Also, under Zone > Speed > Optimization > Image, enabling safe image optimizations—does this count as a transformation and incur additional charges?
We would greatly appreciate an expert review of our account to confirm that we have correctly disabled the Transformation feature and ensure we are no longer being charged for it. Because I think better investing into Business plans rather than using the transformations, because for this we can manually do with our codes.
As a small startup, this unexpected issue has created significant challenges, even delaying one of our employees’ salaries. Your support in resolving this matter would mean a great deal to us.
Thank you for your understanding and assistance. Please check last message of Case Number 01319464
