Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I hate to say this, but you can send more garbage than that. Subrequests have to be begun within 15 seconds, but they themselves can stream data for far longer. We actually support the TransformStream API to allow you to stream your garbage back and not keep it in memory as well.

Beyond that, we support the WebCrypto API, so you are welcome to generate a near infinite amount of cryptographically secure random garbage, and we'll even help out with some from our lava lamps [1].

1- https://www.fastcodesign.com/90137157/the-hardest-working-of...



I can't even load the page, so your miles ahead of me!

If anyone at Cloudflare cares to take a look, here's what I get:

> Server Error

> Our network is literally on fire

> Ray ID: 3fb0bf524995797f

> Your IP address: 172.58.40.122

> Error reference number: 502

> Cloudflare Location: Seattle

2nd try had an Error reference number of 524, with everything else being the same.

Shenanigans like this are why I stopped using Cloudflare on my websites, better to have something I can debug and avoid a party MitM all my connections, than to gain a fleeting bit of "reliability" or "security" that Cloudflare supposedly offers.


I believe "Our network is literally on fire" is an error from Ghost.io, the platform we use to host our blog.


Shouldn't your edge be caching this static article? I don't see why each page needs to be custom generated...


It does cache, yes. But there's a TTL on the cache since we want to be able to make updates to the page if needed.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: