Follow-up #901 - Align CSRF troubleshooting with bundled webserver configs - #910
Merged
Merged
Conversation
…nfigs Commit 533acef6bd (zammad/zammad#6305) changed the recommended proxy setup: an outer proxy can overwrite X-Forwarded-Proto after Zammad's own Nginx sets it, so the bundled configs now blank Forwarded, X-Forwarded-Scheme and X-Forwarded-Ssl, and the Docker images take NGINX_SERVER_SCHEME=https. Update the 'CSRF Token Errors' troubleshooting section accordingly: describe both causes, add the three blanked headers to the Nginx variant, and point Docker Compose users to the HTTPS scenarios page that #901 already extended.
ArtifactsProduced during runtime |
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.
Commit 533acef6bd (zammad/zammad#6305) changed the recommended proxy setup: an outer proxy can overwrite X-Forwarded-Proto after Zammad's own Nginx sets it, so the bundled configs now blank Forwarded, X-Forwarded-Scheme and X-Forwarded-Ssl, and the Docker images take NGINX_SERVER_SCHEME=https.
Update the 'CSRF Token Errors' troubleshooting section accordingly: describe both causes, add the three blanked headers to the Nginx variant, and point Docker Compose users to the HTTPS scenarios page that #901 already extended.