Hey all,
I came across this article describing a work around for using Cloudflare DNS with Webflow
It seems straight forward enough and I’d be happy to test it out on one of my own projects.
But does anyone fully understand the technical and security implications of this method?
I wouldn’t want to implement this for a client without knowing it was 100% legit.
Thanks in advance if anyone can share their knowledge,
Dave
Here is my site Read-Only: LINK
(how to share your site Read-Only link)
I haven’t gone through it with a fine-tooth comb but in general it looks pretty solid. I think I might test this out on some simple sites to see how it does with image optimization.
However one big gotcha up front is that you cannot disable HTTPS on webflow sites which use ECommerce, Logic, or Memberships.
@webdev Is the one to hire if you’re looking for someone to help you improve your site hosting setup & performance.
This looks interesting but no, I haven’t yet tried this.
It does not look very straightforward to me unless you’re very technical.
You also have to think through assets stored in RichText and the CMS, though, this may cover that.
Also something to be aware of is Webflow can at anytime change something on there end that totally breaks this setup, without any warning. That’s possible if their update doesn’t negatively impact their normal usage. They aren’t supporting this workaround.
A quick scan of the comments on the post reveal issues like this:
…however, not all images are being copied to the assets sub domain, only a handful of images are. Majority of images are not.
I’m pretty sure I can tell you what iit is. I’m gonna go ahead and bet if you inspect the page and select the missing image you’re gonna see it’s an scr set. So for responsive images across breakpoints
I’d expect some gotcha’s like this that will take time to investigate and maybe find a workaround for.
I would use caution.