Chromium's Cookies() API can lose or normalize Secure, SameSite, and HttpOnly attributes during the AddCookies → navigate → Cookies() round-trip. This caused cookies like cf_clearance (set with Secure=true, SameSite=None) to be overwritten with Chromium's defaults (Secure=false, SameSite=Lax). Now updateCookies() looks up existing cookies in the jar first. For cookies that already exist, only Value and Expires are updated — security attributes are preserved from the original. New cookies from the server are still written with all their attributes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
9.1 KiB
9.1 KiB