fix(core): respect forwarded headers for base URL detection #13365
+11
−1
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.
☕️ Reasoning
In containerized environments (like Docker) or multi-tenant setups behind a reverse proxy,
Request.urloften reflects the internal network address (e.g., http://0.0.0.0:3000) rather than the public-facing domain.When
trustHostis enabled, the library should prioritize X-Forwarded-Host and X-Forwarded-Proto headers to reconstruct the application's base URL. Without this, callbackUrl validation fails because the incoming URL behaves as a mismatch against the detected internal base URL, leading to incorrect redirects🧢 Checklist
🎫 Affected issues
Potential issue fixes: #8154
📌 Resources