ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When a Flask user logs in but the session disappears after a redirect, the culprit is often the secret key or cookie settings. This guide walks through the symptom, root causes, ordered checks, fixes, and escalation steps to restore session persistence.
Goal: Verify if Chrome’s SameSite=None; Secure requirement is enforced for cookies set by service‑worker‑generated fetch requests that target a different origin. Context: The SameSite=None; Secure rule is documented for all request types, but it is unclear whether the enforcement applies when the Set‑Cookie header originates from a service worker rather than
The goal is to maintain a cross‑site authentication flow that relies on a session cookie set on a third‑party domain (e.g., api.auth‑provider.com) while the user interacts with the main application (app.example.com). The cookie is set with SameSite=None to allow cross‑origin requests, and the server returns it over HTTPS. In local development the request ori
flask
chrome
safari