Marc-André Bombeck 5a875d2840 fix(auth): issue a Secure session cookie under the __Host- prefix ...

A cookie named healthlog_session can be set by any host under the same
registrable domain, so a page on a sibling subdomain could plant a session of
its choosing in a visitor's browser. Wherever the session cookie is Secure it
is now issued as __Host-healthlog_session, which a browser accepts only from
this exact host. Plain-HTTP installs, which cannot hold a __Host- cookie,
keep the old name.

Nobody is signed out: the old name is still read after the new one, a
session found under it is re-issued under the new name and the old cookie
expired, and a browser holding the new cookie is never answered from the old
one. Every reader and writer goes through one module, which the proxy, the
native-caller check, the native handoff and the OIDC callback use; the
session-surface guard follows the new reader.

2026-10-25 17:44:31 +01:00

..

call-route.ts

fix(auth): issue a Secure session cookie under the __Host- prefix

2026-10-25 17:44:31 +01:00

factories.ts

fix(auth): issue a Secure session cookie under the __Host- prefix

2026-10-25 17:44:31 +01:00

parity.ts

fix(analytics): cut every summary window on the request's clock

2026-10-24 12:14:33 +02:00