Issues with embed

Forum|Forum|2 years ago
November 28, 2023
3 replies
901 views

Hello.

Just recently, the embed instructions noted here have stopped working:
https://help.calendly.com/hc/en-us/articles/223147027?tab=advanced#3

Using the invocation code:

Calendly.initInlineWidget({ url: 'https://calendly.com/d/FORMIDREMOVED?hide_gdpr_banner=1', parentElement: document.getElementById('calendly-modal-body'), prefill: {} });

Spawns a request to Calendly that ultimately returns this response

Age: 9545 cf-cache-status: DYNAMIC cf-ray: 82d4ad0a0b103705-YYZ Content-Encoding: br Content-Type: text/html; charset=utf-8 Date: Tue, 28 Nov 2023 18:29:21 GMT Last-Modified: Tue, 28 Nov 2023 15:50:04 GMT Server: cloudflare Strict-Transport-Security: max-age=31536000; includeSubDomains; preload Vary: Accept-Encoding, Origin Via: 1.1 192b5dfe0d3306c6761973a7786a01d4.cloudfront.net (CloudFront) x-amz-cf-id: qnDkzkCQ-DxfUc_z4Pp1jZA24f5UoczK1oqvza1rvhS0u98DWrPW4A== x-amz-cf-pop: YUL62-C2 x-amz-version-id: EVin17i.0_5u4mmzATuQGsDtuQywgDL1 x-cache: Hit from cloudfront X-Content-Type-Options: nosniff X-Frame-Options: DENY

The X-Frame-Options: DENY is the kicker, since the Calendly.initInlineWidget call spawns within an iFrame.

In other words, the javascript says: load _this_ in an iFrame

The iframe body request says: no iFrames allowed.

New bug?

embed

This topic has been closed for replies.

Best answer by marion-calendly

Hi @LemonadeLXP !

We experienced an incident earlier that affected routing forms (see our Status page) which would have resulted in the embed code loading a page that could not be displayed in an iframe. Based on the timing of your post, I think you may have been impacted by this.

If you’re still seeing the same result, I would also recommend checking that the link you have passed to the code is valid (e.g. by loading it in your browser directly). Our 404 page also has X-Frame-Options: DENY so this is the most common reason for seeing that in our embed.

marion-calendlyAnswer

Employee

Hi @LemonadeLXP !

We experienced an incident earlier that affected routing forms (see our Status page) which would have resulted in the embed code loading a page that could not be displayed in an iframe. Based on the timing of your post, I think you may have been impacted by this.

If you’re still seeing the same result, I would also recommend checking that the link you have passed to the code is valid (e.g. by loading it in your browser directly). Our 404 page also has X-Frame-Options: DENY so this is the most common reason for seeing that in our embed.