If you want to visit the page directly without CloudFlare, go to http://trombone.zapto.org instead.
HTTP/1.1 200 OK
Server: mTCP HTTPServ Mar 7 2020
Date: Sun, 17 Apr 2022 00:30:00 GMT
Content-Type: text/html
Content-Length: 5355
Expires: Fri, 14 Oct 2022 00:30:00 GMT
Last-Modified: Sun, 17 Apr 2022 00:02:00 GMT
Connection: keep-alive
The page loads very interestingly. Each paragraph loads separately, one at a time down the page. I'm guessing because of the bandwidth limitation.Really neat, especially the slow loading. When I saw cloudflare on the page, I thought it was faked with javascript, but it was real!
Interesting how chromium will start rendering no matter how little information does it have (:
Disclaimer: I work on R2
that will also work in this instance.
you won't however see it slowly send the response as you do on http://trombone.zapto.org/, as cloudflare seems to block until it received the full response from the backend.
No affiliation with cloudflare other than I use them for several sites.
> helps with the default settings of including that in the cache key
I didn't know about response streaming being configurable, it seems to be enabled by default and configurable for enterprise customers: https://support.cloudflare.com/hc/en-us/articles/206049798-S...
I assume due to the (relatively) small response size of this page it buffers regardless.
In the meantime, if you want to visit the page directly without CloudFlare, go to http://trombone.zapto.org instead.
Edit: but also identifying heuristics like lack of JS execution, or potentially client specific http client behaviour
I hope you don’t regularly make such selfish requests to potential DoS victims due to your own arrogance / ignorance.