Reverse proxy and CORS issues¶
Symptoms¶
- local runs work but production browser calls fail
- redirects use the wrong scheme or host
- the management web cannot call the API
Likely causes¶
- forwarded headers are disabled or incompletely trusted
AllowedCorsOriginsis missing the real browser origin- ingress is rewriting scheme or host unexpectedly
Checks¶
- confirm
ForwardedHeaders__Enabled - review trusted proxies or networks
- confirm
AllowedCorsOriginscontains the exact management web origin - verify the public authority URL and host headers seen by the API
Fixes¶
- enable and scope forwarded headers correctly
- correct the browser origin list
- repair ingress host, scheme, or header forwarding
When to escalate¶
Escalate when browser and proxy traces disagree with the API logs after forwarding and CORS settings are corrected.