support for trusted csrf origins #644
Merged
Conversation
This file contains 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
|
CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅ |
|
I have read the CLA Document and I hereby sign the CLA |
InoMurko
force-pushed
the
inomurko/csrf_trusted_origins
branch
from
0309d71
to
019ccbf
Compare
Uxio0
requested changes
Jan 20, 2022
Uxio0
approved these changes
Jan 20, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What was wrong?
Support for CSRF trusted origins https://docs.djangoproject.com/en/3.2/ref/settings/#csrf-trusted-origins
which is useful for different kinds of deployments.
Relevant:
safe-global/safe-config-service#402
#640
Closes #
How was it fixed?
Added reading env CSRF_TRUSTED_ORIGINS and setting CSRF_TRUSTED_ORIGINS.
@gnosis/safe-services