Make the attempt cookie's deletion Secure so a browser honours it
A __Host- cookie is only removed by a Set-Cookie that is itself Secure. The hardening test now checks Secure on every header, deletion included, and the completion tests pin that success and refusal both clear the attempt cookie with Secure, Path=/ and no Domain. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
c757acf525
commit
58fa80bc5b
3 changed files with 31 additions and 9 deletions
|
|
@ -470,8 +470,9 @@ public static class HeimdallAttemptCookie
|
|||
};
|
||||
|
||||
/// <summary>
|
||||
/// The options a deletion carries: only the attempt cookie's Path, which a cookie is matched on. It carries no
|
||||
/// Max-Age, which would take precedence over the expiry Delete writes and leave the emptied cookie alive.
|
||||
/// The options a deletion carries: the attempt cookie's Path, which a cookie is matched on, and Secure, without
|
||||
/// which a browser ignores a Set-Cookie for a __Host- name. It carries no Max-Age, which would take precedence
|
||||
/// over the expiry Delete writes and leave the emptied cookie alive.
|
||||
/// </summary>
|
||||
public static CookieOptions DeleteOptions() => new() { Path = BifrostCookies.Path };
|
||||
public static CookieOptions DeleteOptions() => new() { Path = BifrostCookies.Path, Secure = true };
|
||||
}
|
||||
|
|
|
|||
Loading…
Reference in a new issue