fix: forward proto from reverse proxy #1524
Merged
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.
PR Type
[x] Bugfix
What Is the Current Behavior?
The protocol used on the topmost reverse proxy is not correctly forwarded to the SSR container.
Steps to reproduce:
Install Intershop Helm Charts:
create minimal
values.yaml
file for proxying ICM:Install release:
Forward
pwa.example.local
to127.0.0.1
in your hosts fileCheck the release https://pwa.example.local and observe you are getting mixed content errors
What Is the New Behavior?
The protocol is correctly forwarded to the SSR container using and trusting the
X-Forwarded-Proto
header.Does this PR Introduce a Breaking Change?
[ ] Yes
[x] No
Other Information
AB#90392