From 9ff5c8bd94ade4b70be6a72f00e9df9317b55f66 Mon Sep 17 00:00:00 2001 From: Sluijsens Date: Tue, 10 Nov 2026 23:22:45 +0100 Subject: [PATCH] Docs: frame-src-origins voor ASF (hoofdhost + 2 reserve-hosts) Co-Authored-By: Claude Sonnet 5.5 --- .../contact-forms-module/construction/phase-1-handoff.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aidlc-docs/features/contact-forms-module/construction/phase-1-handoff.md b/aidlc-docs/features/contact-forms-module/construction/phase-1-handoff.md index 1d4709a..60122b9 100644 --- a/aidlc-docs/features/contact-forms-module/construction/phase-1-handoff.md +++ b/aidlc-docs/features/contact-forms-module/construction/phase-1-handoff.md @@ -137,7 +137,7 @@ With `Contact:Enabled=true` and `Captcha:Enabled=true` the host **refuses to sta ### Widget (website session) and CSP - Widget: Friendly Captcha v2 SDK with `sitekey` = `siteKey` from the token response; for the EU endpoint the widget needs `apiEndpoint: "eu"` (`data-api-endpoint="eu"`). The response goes into `captchaToken`. Exact SDK package/events: to be verified by the website session against the SDK docs. -- **CSP** (decision: exact origins, no wildcard): the v2 widget renders in iframes and the provider's CSP guide requires `frame-src` for `*.frcapi.com`. New option `SecurityHeaders:AllowedSiteFrameOrigins` (StrictSite only; empty = header byte-identical to before; origins only, validated at start-up; the admin and relaxed policies never get it). ASF value for now: `SecurityHeaders__AllowedSiteFrameOrigins__0=https://global.frcapi.com`; add `https://eu.frcapi.com` as `__1` when the site switches to the EU region. The resulting directive is `frame-src 'self' https://global.frcapi.com`. No `connect-src`/`script-src` additions are documented by the provider; a browser test with the real widget is still needed. +- **CSP** (decision: exact origins, no wildcard): the v2 widget renders in iframes and the provider's CSP guide requires `frame-src` for `*.frcapi.com`. New option `SecurityHeaders:AllowedSiteFrameOrigins` (StrictSite only; empty = header byte-identical to before; origins only, validated at start-up; the admin and relaxed policies never get it). ASF values (owner decision: main host plus two reserve hosts, exact, no wildcard): `SecurityHeaders__AllowedSiteFrameOrigins__0=https://global.frcapi.com`, `__1=https://global0.frcapi.com`, `__2=https://global1.frcapi.com`. On the switch to the EU region use `https://eu.frcapi.com`, `https://eu0.frcapi.com`, `https://eu1.frcapi.com` instead (together with `Contact__Captcha__Region=eu`). The resulting directive is `frame-src 'self' https://global.frcapi.com https://global0.frcapi.com https://global1.frcapi.com`. No `connect-src`/`script-src` additions are documented by the provider; a browser test with the real widget is still needed. - Privacy (provider statements, v2 docs): "Friendly Captcha does not rely on user tracking or cookies for its protection service". **Region `global`**: the visitor's IP address can be processed outside the EU. **Region `eu`** (dedicated endpoint "hosted in Germany"; paid Advanced/Enterprise plan): "personal information (i.e. visitor IP addresses) never leave the EU". The site's privacy page must name the captcha provider, the processing of the visitor's IP address for the challenge, and which region is in use; commercial use needs a paid plan with the provider. For a test or a launch without a paid plan keep `Contact:Captcha:Enabled=false`. ### ASF host (`Api.AndreaSlopFotografie`)