7a192d33fd
Automatic update from web-platform-testsCookie Store: Tentatively deflake special names test The "expires" cases are flaky on all platforms on the bots, although I can't reproduce locally. The test case sets a cookie that expires "now" then expects it can't read it. It may be flaky due to "now" being slightly different between processes, threads, and libraries, allowing the read to succeed. Set the expiry date to be an hour before "now", which should be sufficient. Bug: 829761 Change-Id: Icda1891310dd0a56769877f32405226390e729de Reviewed-on: https://chromium-review.googlesource.com/999743 Commit-Queue: Joshua Bell <jsbell@chromium.org> Reviewed-by: Victor Costan <pwnall@chromium.org> Cr-Commit-Position: refs/heads/master@{#548903} wpt-commits: a4c17db5364ca97ffa9bb76f9c8e6e155ecd3ddb wpt-pr: 10349 wpt-commits: a4c17db5364ca97ffa9bb76f9c8e6e155ecd3ddb wpt-pr: 10349
This directory contains tests for the Async Cookies API.
Note on cookie naming conventions
A simple origin cookie is a cookie named with the __Host- prefix
which is always secure-flagged, always implicit-domain, always
/-scoped, and hence always unambiguous in the cookie jar serialization
and origin-scoped. It can be treated as a simple key/value pair.
"LEGACY" in a cookie name here means it is an old-style unprefixed
cookie name, so you can't tell e.g. whether it is Secure-flagged or
/-pathed just by looking at it, and its flags, domain and path may
vary even in a single cookie jar serialization leading to apparent
duplicate entries, ambiguities, and complexity (i.e. it cannot be
treated as a simple key/value pair.)
Cookie names used in the tests are intended to be
realistic. Traditional session cookie names are typically
all-upper-case for broad framework compatibility. The more modern
"__Host-" prefix has only one allowed casing. An expected upgrade
path from traditional "legacy" cookie names to simple origin cookie
names is simply to prefix the traditional name with the "__Host-"
prefix.
Many of the used cookie names are non-ASCII to ensure straightforward internationalization is possible at every API surface. These work in many modern browsers, though not yet all of them.