Private
Public Access
Purge the service worker's authenticated-page cache on logout (S3)
PAGES_CACHE held every cached navigation response (including authenticated article pages) with no logout-time purge, so a later offline navigation on a shared or account-switched device could still serve another user's cached pages. Logout is a plain POST, so the fetch handler now special-cases that request: it deletes PAGES_CACHE and lets the real logout request through, with no race against the navigation that follows since it's synchronous with the same request. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
1 parent
b52ba2be8a
commit
d7b433e580
2 files changed
+20
-1
No files matched your search
@@ -32,6 +32,11 @@ def test_service_worker_is_served_at_root_with_correct_type_and_scope(client):
|
||||
assert 'self.addEventListener("fetch"' in body
|
||||
# Mutations must stay network-only, never intercepted.
|
||||
assert 'request.method !== "GET"' in body
|
||||
# Logging out must purge PAGES_CACHE so a later offline navigation on
|
||||
# a shared/account-switched device can't serve another user's
|
||||
# previously cached authenticated pages.
|
||||
assert "caches.delete(PAGES_CACHE)" in body
|
||||
assert reverse("accounts:logout") in body
|
||||
|
||||
|
||||
@pytest.mark.django_db
|
||||
|
||||
Reference in new issue
Block a user