Refresh HiveGrid Cloud reference snapshot
This commit is contained in:
1 parent
5e99e14772
commit
7f88026f79
5955 files changed
+1177325
-188362
No files matched your search
@@ -1,13 +1,10 @@
|
||||
/**
|
||||
* CORS-allowlist matcher for the marketing-funnel capture endpoint (Phase 05 #78).
|
||||
* CORS-allowlist matcher retained for the retired browser-capture drain response.
|
||||
*
|
||||
* The endpoint is intentionally public so external landing-pages can ingest
|
||||
* leads, but the Origin header is matched against `MARKETING_ALLOWED_ORIGINS`
|
||||
* (comma-separated env list). Wildcards are supported via a single leading `*`
|
||||
* in the host (e.g. `https://*.hivegrid.de`).
|
||||
*
|
||||
* Server-to-server bots can spoof Origin — this layer is one of three (origin
|
||||
* allowlist, rate-limit, optional Turnstile). It does NOT replace rate-limiting.
|
||||
* `/api/leads/capture` no longer writes and always returns 410. The allowlist
|
||||
* only permits known stale browser deployments to read that structured response
|
||||
* cross-origin during the R-LEADS drain window. Native intake is authenticated
|
||||
* server-to-server at `/v1/platform/leads` and does not use this helper.
|
||||
*/
|
||||
|
||||
export function parseAllowedOrigins(raw: string | undefined | null): string[] {
|
||||
|
||||
Reference in new issue
Block a user