Security CORS local versus production drift response

When this happens

Use this when it works locally but fails only on the deployed server. Do not stop at the screen message; validate runtime version, environment variables, file paths, locale, timezone, and permissions first.

Symptom checklist

• CORS appears repeatedly in the Security UI or logs.
• CSP, CORS, CSRF, JWT, cookies, WAF rules differs between successful and failed requests.
• The issue appears only after separating policy block from application permission error.
• It often follows deploys, permission changes, configuration edits, or data refreshes.

Likely causes

• CORS specifically changes the investigation surface for Security: verify the exact failing object, route, user, and timestamp before applying the broader pattern.
• The preflight response lacks the method, header, credentials, or origin required by the browser.
• CSP blocks script, style, image, frame, or connect targets that the app now uses.
• Server-rendered HTML differs from the first client render during hydration.
• Nonce or hash values are generated differently between middleware and page output.
• The backend works with curl but fails in the browser because browser policy is stricter.
• For the local versus production drift case, the first useful clue is runtime version, environment variables, file paths, locale, timezone, and permissions.

First 1-minute checks

1. Write down the first failure time, latest change, affected user, path, and object ID.
2. Compare CSP, CORS, CSRF, JWT, cookies, WAF rules for success and failure in the same window.
3. Test the hypothesis: browser-side failure caused by CORS/CSP policy, preflight headers, SSR hydration mismatch, nonce/hash drift, or client-only state.
4. Classify this as local versus production drift: runtime version, environment variables, file paths, locale, timezone, and permissions.
5. Capture current values before changing configuration.

First evidence

Treat CORS as a local versus production drift case. First collect evidence for runtime version, environment variables, file paths, locale, timezone, and permissions.

Output examples

Normal output

Runtime, env values, paths, and permissions match the documented production baseline.

Failing output

Production uses a different version, env var, path, locale, timezone, or user.

Output-to-action branches

• It works locally but fails only on the deployed server.
  Print effective runtime state from the failing process, not only from the login shell.
• The working and failing outputs differ.
  Act on the differing layer first: For CORS, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Command output is normal but users still fail.
  Separate browser cache, cookies, permissions, and network location before declaring it fixed.

Do not do this

• Do not trust CLI output if the web worker, service, or container runs as another user.
• Do not change multiple layers before identifying the failing layer.
• Do not delete production data, grant broad permissions, or disable security controls as a first response.

Evidence quality

Auto-generated operator draft: includes issue-specific causes, commands, output branches, and unsafe-action warnings. Official-source links and real incident validation are queued for enrichment.

Commands to run first

grep -R "CORS" ./logs

curl -I https://example.com

grep -R "CORS" ./logs

jwt decode TOKEN

curl -H "Origin: https://app.example.com" -I https://api.example.com

curl -i -X OPTIONS https://api.example.com/path -H "Origin: https://app.example.com" -H "Access-Control-Request-Method: POST"

grep -R "Content-Security-Policy\|Access-Control-Allow\|hydration" ./logs src

npm run build

printenv | sort && pwd && id

Fix order

1. Record the full CORS message, failing URL, user, object ID, and latest change.
2. Collect issue-specific evidence for browser-side failure caused by CORS/CSP policy, preflight headers, SSR hydration mismatch, nonce/hash drift, or client-only state.
3. Compare the failing case with a successful case before editing settings.
4. If this is the local versus production drift branch, Print effective runtime state from the failing process, not only from the login shell.
5. Re-check with the same command and URL, then record the normal output.

Actions by cause

• For CORS, apply the fix only after reproducing the same condition and saving the before/after evidence for this exact code.
• Check the browser network panel and preflight response before changing application logic.
• Allow only the required origin, method, and headers for CORS.
• Add CSP directives for the exact resource target instead of disabling CSP.
• Move client-only values behind hydration-safe effects or placeholders.
• Add an automated browser check for the failing route.
• For the local versus production drift branch, Print effective runtime state from the failing process, not only from the login shell.

Evidence links

• MDN CORS errors official
• MDN Content Security Policy official
• OWASP Cheat Sheet Series official

Verification metadata

• operator-draft
• official-reference-linked
• 2026-07-23

Update queue

• Review cadence
  weekly-source-review
• Next enrichment
  Add one official-source check and one real output example for Security CORS.

Environment-specific checks

• Shared hosting, proxies, VPNs, or CDN layers can change policy block from application permission error results.
• Do not trust only the Security UI; compare command output.
• Japanese hosting panels may show completion before DNS or SSL fully propagates.
• Test from both office and external networks.

Prevent it next time

• Store normal examples for CSP, CORS, CSRF, JWT, cookies, WAF rules.
• Add origin allowlists, token expiry, SameSite, WAF exceptions to the release checklist.
• Keep recurring errors in the same note format.
• Split alerts by error rate, latency, certificates, disk, and permission changes.

Related notes

• Security 403 first triage response
• Security CSRF first triage response
• Security CSP first triage response
• Security CORS first triage response
• Security WAF block first triage response
• Security rate limit first triage response
• Security OAuth redirect first triage response
• Security JWT expired first triage response