-
Notifications
You must be signed in to change notification settings - Fork 429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add option to disable secure cookies and configure samesite
#3441
feat: add option to disable secure cookies and configure samesite
#3441
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Uffizzi Preview |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3441 +/- ##
=======================================
Coverage 95.91% 95.91%
=======================================
Files 1092 1092
Lines 34003 34005 +2
=======================================
+ Hits 32613 32615 +2
Misses 1390 1390 ☔ View full report in Codecov by Sentry. |
samesite
9ebe844
to
22249a5
Compare
Thanks for submitting a PR! Please check the boxes below:
pre-commit
to check lintingdocs/
if required so people know about the feature!Changes
Adds an environment variables to disable using secure cookies and configuring the value of
samesite
. This is to be used for deployments inside a private network without a domain / ssl cert.How did you test this code?
Used a combination of
SAME_SITE_COOKIE: strict
andUSE_SECURE_COOKIES: false
to confirm that running the Flagsmith application over http on an internal IP address correctly sets the token. Note that the defaults are set to the same as the previous values.