From ffa14b0fdf1d3520a85235ab15b8b2a23bb0771a Mon Sep 17 00:00:00 2001 From: Eric Lawrence Date: Tue, 21 Jan 2025 14:07:14 -0800 Subject: [PATCH] Update EXPIRES info with clock skew Firefox and Chromium adjust the EXPIRES value with the computed clock-skew as calculated using the response's DATE header. --- files/en-us/web/http/headers/set-cookie/index.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/files/en-us/web/http/headers/set-cookie/index.md b/files/en-us/web/http/headers/set-cookie/index.md index e10ddfd66097f78..315a1c7e5dcb3a9 100644 --- a/files/en-us/web/http/headers/set-cookie/index.md +++ b/files/en-us/web/http/headers/set-cookie/index.md @@ -101,7 +101,8 @@ Set-Cookie: =; Domain=; Secure; HttpOnl > [!WARNING] > Many web browsers have a _session restore_ feature that will save all tabs and restore them the next time the browser is used. Session cookies will also be restored, as if the browser was never closed. - When an `Expires` date is set, the deadline is relative to the _client_ the cookie is being set on, not the server. + When an `Expires` date is set, the deadline is relative to the _client_ the cookie is being set on, not the server. However, the server's `Date` header will be used to compute the clock skew between the + client and the server, and the `Expires` date will be adjusted accordingly. - `HttpOnly` {{optional_inline}}