Fixed invalid default value for SESSION_DOMAIN #354
Merged
Conversation
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
As from commit 522cbd4 the default value for SESSION_DOMAIN is now set to "apc" if it's not supplied. This will lead to CSRF token validation failures as described on cachethq/cachet#2741 (comment) With this commit the SESSION_DOMAIN will just be empty when not explicitly configured.
Contributor
Author
|
Will probably also fix #341. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As from commit 522cbd4 the default value for
SESSION_DOMAIN is now set to "apc" if it's not supplied. This will lead to
CSRF token validation failures as described on
cachethq/cachet#2741 (comment)
With this commit the SESSION_DOMAIN will just be empty when not explicitly
configured.