You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Scope the insecure-origin warning and document the trusted-origins knob
The Secure-cookie warning fired whenever any trusted origin was http,
which includes the plain http://localhost default, so every local boot
printed it. Warn only for the mixed case an operator opts into: an http
alias alongside an https canonical URL, where the canonical origin
really does lose Secure cookies.
Move the resolver below loadConfig with the other env knobs and state
why each rejected origin shape is refused rather than trimmed. Cover
the rejected shapes as a table, plus the blank-list and bare-hostname
cases.
"[executor] HTTP trusted origins require session cookies without the Secure attribute. Use HTTPS-only origins to keep session cookies transport-secure.",
86
+
"[executor] EXECUTOR_TRUSTED_ORIGINS contains an http:// origin, so session cookies drop the Secure attribute for every origin — including the https:// canonical URL. Use https:// aliases to keep session cookies transport-secure.",
75
87
);
76
88
}
77
89
// Always resolved (generated + persisted when no env is set); this guards only
0 commit comments