Skip to content

Content Security Policy ​

If your site sends a Content-Security-Policy header, allow the domains used by the integration you chose. Replace https://canardform.app with the address of your forms if it differs (publicUrl).

DirectiveDomainsFor
script-srchttps://cdn.jsdelivr.netthe SDK loaded from jsDelivr (HTML page without a build tool)
connect-srchttps://canardform.appreading the published fields and sending answers (SDK, React, Vue, JavaScript)
form-actionhttps://canardform.appnative HTML form sent directly to Canard Form
frame-srchttps://canardform.appCMS and iframe embedding
script-src, frame-src, style-src, connect-srchttps://hcaptcha.com https://*.hcaptcha.combot verification, if the form requires it

Example for the SDK with bot verification:

script-src 'self' https://cdn.jsdelivr.net https://hcaptcha.com https://*.hcaptcha.com;
connect-src 'self' https://canardform.app https://hcaptcha.com https://*.hcaptcha.com;
frame-src https://hcaptcha.com https://*.hcaptcha.com;
style-src 'self' https://hcaptcha.com https://*.hcaptcha.com;

The SDK example is a <script type="module"> written in the page: a policy without 'unsafe-inline' blocks it. Move that code to a file on your site, or give it a nonce.

Released under the MIT License.