Hey Admin, What are the Advantages and Disadvantage i will face when i will connect a custom domain with infinityfree hosting as well as cloudfare???
1 Like
The only downside I’ve found is that you still have to stick to the limits of the free hosting account, and if Cloudflare goes down (like it did a few weeks back), your site becomes inaccessible.
The main advantage is that Cloudflare is pretty good at blocking DDoS attacks. It also has some caching on their side, so it can reduce hits and speed up your site for some visitors
–Edit–
I’m not counting the 30 minutes (per domain) it took me to set everything up as a downside.
6 Likes
Cloud you please explain this in more detail? And i heard that in pages powered by JavaScript , hits are not count. Explain in more detail, please.
Even if you’re page uses Javascript, if the request is made to the infinityfree servers, the relevent hits are counted.
However, if you’re using Cloudflare, and the page\script is cached on their side, then the request never reaches the infinity free server, and so no hits are counts
4 Likes
Website files and other assets will be stored in infinityfree usually, and domain is connected with cloudfare also, so when JavaScript pages is open, no hits will be send on infinityfree? If it will be PHP page, then hits would definitely count? Explain me in detail, how hit will count and not count.
With straight HTML and Some javascript pages, Couldflare can cache the page. This means that they keep a copy of the page on their server, and when someone visits the site, they’ll display it from their copy rather than the copy on InfinityFree
In this case, no hits are counted, because no connection has been made to the Infinity Free server
However, with PHP pages (I think), and some javascript pages, Cloudflare can’t cache them, so the hits will count
Caching levels and lifetime can be configured in the Cloudflare dashboard.
5 Likes
The idea is that Cloudflare caches content that’s the same for everyone, but doesn’t cache content that might be different for individual visitors.
By default, Cloudflare only caches static content, like CSS, Javascript code and images.
Cloudflare doesn’t cache HTML by default. Cloudflare has no way to tell whether the HTML code that’s sent to your visitor is static content, or generated by a dynamic application (like anything using PHP). If you want it to be cached, you can configure that in Cloudflare.
Just don’t do that if you’re using PHP, because then things won’t work correctly.
The main advantage from Cloudflare is that they cache content and serve it from hundreds of regional locations around the globe, which speeds up your site and reduces load on your hosting account. DDoS protection is frequently named, but the kind of DDoS protection which they are actually good at doesn’t really matter if you’re on a shared server, and their protection against web attacks is not that good in my experience.
The main disadvantage from Cloudflare is that it’s an additional moving part you need to setup. You need to configure your own DNS records there and SSL configuration can be a bit more involved, and you can break you website if you make a mistake. It’s not rocket science, but skipping Cloudflare is definitely simpler.
4 Likes
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.