![]() ![]() If you have a specific domain you’d be IFRAMEd in, you can restrict it to that trusted domain for safety. You’ll have to decide whether you’re ok with clickjacking risks, etc. I’ve never seen that done, but can’t hurt to ask.Īlthough Webflow blocks this to mitigate the risk of membership hacking, in your case, you’re not actually using Webflow’s memberships. iFrame Generator is the best and free online iFrame generator tool (iframe code generator) with various options and live iframe Preview option for Webmasters, Bloggers and Web Designers to embed any online page or HTML document to any page or website. You might contact Webflow and see if they have a means to change that rule per-site. Select Options for Your iFrame Name: Other iFrame Options. embed, for that special purpose, or proxy your whole site for everyone, and rewrite that header. I’m not sure what your use case here is for being embedded in an IFRAME, but you can create, e.g. hack your headers with a reverse proxy.completely rebuild your site, this time, no memberships or ecommerce activation.Even Webflow support cannot remove memberships or commerce, apparently. If you go here, you can see Webflow’s memberships sign-up page. You may never have used it, but at some point you activated it or the template you purchased had it activated. The reason why is that you have memberships enabled. It tells browsers that your site can only be IFRAMEd inside of pages from the same domain. ![]() Here’s a codepen demonstrating it as well. Webflow sites published to custom domains do not have that policy header. ![]() Specifically, it looks like this content-security-policy: frame-ancestors 'self' This happens because web requests made to *.webflow.io return an HTTP header that specifies a content-security-policy restricting where that content can be IFRAME-hosted. The first one is the live site on a custom domain, and the second is the staging site on webflow.io. I did this: ĭidnt get around to designing anything yet so I just tested with a few templatesīoth of these are the same site. sadly though it didnt and I am sort of hoping its the generated iframe thats the problem although I cannot see what I did wrong. I just took the generated iframe and plonked it into some html in an online editor to see if it worked. As long as you’re doing a simple embed you should be fine. Can you share the link to the actual site where you have the IFRAME embedded?Īlso, IFRAMEs are quite simple, but there are challenges as well- scrollbars, adapting to responsive breakpoints, security “across the frame” etc. My guess is something’s wrong with the iframe code, or that perhaps the containing site is breaking it on render. It’s difficult to guess what you’re seeing without a readonly link to your site, and seeing the actual code you’re embedding in your containing site. To test this, try embedding these two sites into your playcode.io page īoth of these are the same site. However you cannot IFRAME embed content from the *.webflow.io staging domain to another domain. YES you will be able to IFRAME-embed your Webflow site in another website, once it’s on a paid plan and published to a custom domain name. Can I have a webflow page in a generated iframe? General ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |