docs(rum-util): add Backend CORS section to integration checklist#113
Merged
Conversation
The README documented the required CSP additions but not the backend CORS allowedHeaders — which is what let the CORS preflight breakage slip through when saga-dash enabled RUM. Add a 'Backend CORS' step listing the 7 Datadog tracing headers, the echo-is-auto-covered note, and the validate-on-main-not-previews gotcha. Re hipponot/iac#358.
❌ Test Results
Package Results
Commits
LinksUpdated: 2026-06-02T15:45:23.169Z |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
hipponot/iac#358 — the
@saga-ed/soa-rum-utilREADME documents the required CSP additions but not the backend CORSallowedHeaders. That omission is what let the CORS-preflight breakage slip through when saga-dash first enabled RUM (dash.wootdev.comcould no longer reach IAM).What
Adds a "Backend CORS" step (#7) to the integration checklist, between CSP and Bootstrap:
traceparent,tracestate,x-datadog-*) thatallowedTracingUrlsinjects on every matching cross-origin fetch, and that each backend must list inallowedHeaders.Access-Control-Request-Headersare auto-covered.OPTIONScarries no cookies/custom headers, sox-saga-preview-*routing never applies — it always hits main), with a ready-to-runcurl -X OPTIONScheck.Docs only.