fix(prerenderer): configure trust proxy#596
Merged
Conversation
There was a problem hiding this comment.
Pull Request Overview
This PR fixes HTTPS redirection issues in the prerender server by configuring Express to trust proxy headers. The change prevents the problematic redirect chain where HTTPS requests are incorrectly redirected to HTTP and then back to HTTPS.
- Configures Express to trust the
X-Forwarded-Protoheader from proxies
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
DeviaVir
force-pushed
the
prerender-trust-proxy
branch
from
b228d76 to
65edd1d
Compare
DeviaVir
added a commit
that referenced
this pull request
Sep 24, 2025
* feat(prerenderer): add prom + 503 overload protection * fix(prerenderer): configure trust proxy to fix http -> https redirects (#596)
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.
This should resolve issues with redirecting, e.g. this chain currently happens:
https://blockstream.info/nojs->http://blockstream.info/nojs->https://blockstream.info/nojsMostly because the server doesn't trust the proxy's
X-Forwarded-Protoheader.