Change setDomainCookies to no #4
Open
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
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.
It appears that the default value for setDomainCookies is not amenable when using multiple subdomains (when you do not want to share the cookies).
For example, I have blog.alumniq.com and {random-client}.alumniq.com, and there is no need to share the Mango session between them. In fact, having the mango session cookies at all prevents me from being able to log into the other sites, because I then end up with multiple
cfidandcftokencookies.Setting
this.setDomainCookies="no";in my Mango installs has resolved this cookie conflict with my other subdomains.