fix(converters): Ensure x-forwarded-proto is set to http when running locally #887
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.
Discussed in #686 over at
opennextjs-cloudflare
next-auth
and possibly more libraries rely on thex-forwarded-proto
header to behttp
to work out of the box when run locally. Innext start
ornext dev
they set this tohttp
when ran locally.To make
opennextjs-cloudflarejs preview
and our node converter when running OpenNext locally behave the same we would want to set this header tohttp
. This would make the user not have to set anAUTH_URL
in those modes.