|
|
|
|
|
by jrochkind1
894 days ago
|
|
I continue to be super confused by this. The blog post says, as you quote: > we made it clear that customers can serve video and other large files using the CDN so long as that content is hosted by a Cloudflare service like Stream, Images, or R2. But when I click through to the specific CDN terms it still says: > Unless you are an Enterprise customer, Cloudflare offers specific Paid Services (e.g., the Developer Platform, Images, and Stream) that you must use in order to serve video and other large files via the CDN. A plain reading of this would still make me think putting the CDN in front of video files on R2 was forbidden. It is now clear that you can use (the very expensive) Stream to serve video, sure. |
|
> The Cloudflare Developer Platform consists of the following Services: (i) Cloudflare Workers, a Service that permits developers to deploy and run encapsulated versions of their proprietary software source code (each a “Workers Script”) on Cloudflare’s edge servers; (ii) Cloudflare Pages, a JAMstack platform for frontend developers to collaborate and deploy websites; (iii) Cloudflare Queues, a managed message queuing service; (iv) Workers KV, D1, Durable Objects, Vectorize, Hyperdrive, and R2, storage offerings used to serve HTML and non-HTML content...
Key part being the last bit there, they specifically call out products which can be used to serve non-html content as part of the Dev Plat, and Workers is not one of them.
Cloudflare employees in the past have specifically and repeatedly say CDN in front of R2 is fine, but nothing about Workers except really old posts that predate the ToS changes and the blog post.