Hacker News new | ask | show | jobs
by kondbg 1614 days ago
Using Cloudflare to proxy B2 content seems like it directly violates Cloudflare's ToS.

https://www.cloudflare.com/terms/

> 2.8 Limitation on Serving Non-HTML Content

> The Services are offered primarily as a platform to cache and serve web pages and websites. Unless explicitly included as part of a Paid Service purchased by you, you agree to use the Services solely for the purpose of (i) serving web pages as viewed through a web browser or other functionally equivalent applications, including rendering Hypertext Markup Language (HTML) or other functional equivalents, and (ii) serving web APIs subject to the restrictions set forth in this Section 2.8. Use of the Services for serving video or a disproportionate percentage of pictures, audio files, or other non-HTML content is prohibited, unless purchased separately as part of a Paid Service or expressly allowed under our Supplemental Terms for a specific Service. If we determine you have breached this Section 2.8, we may immediately suspend or restrict your use of the Services, or limit End User access to certain of your resources through the Services.

If this was truly acceptable and not in some grey area, why doesn't Backblaze simply route all downloads through Cloudflare by default, rather than having each individual customer go through the hassle of setting this up?

3 comments

Backblaze is part of the "Bandwidth Alliance", different rules apply:

https://www.cloudflare.com/en-gb/bandwidth-alliance/

With this said, I believe there are restrictions for certain types of content (eg: video). Cloudflare needs to be more clear here to avoid confusion.

The page says that the Bandwidth Alliance means that partners will charge less or no egress to cloudflare.

I'm not seeing it saying anything about different rules applying regarding CloudFlare ToS such as "2.8 Limitation on Serving Non-HTML Content" to Bandwidth Alliance sources.

But has that been said somewhere I'm not seeing? Would love to see it!

Doesn't this violate net neutrality ... ?
If you only use this for "standard" CDN assets (like pictures that are part of your website styling rather than as an image host) and you also host your website on Cloudflare, I think it should be ok.
> If this was truly acceptable and not in some grey area, why doesn't Backblaze simply route all downloads through Cloudflare by default, rather than having each individual customer go through the hassle of setting this up?

Because Backblaze makes more money charging you for repeated downloads?