Revision 95fcc7595a9e0eaec42034d056cef4e2de04cfd1 authored by Sebastian Hengst on 11 April 2018, 09:29:31 UTC, committed by moz-wptsync-bot on 11 April 2018, 09:29:31 UTC
gecko-commit: 9fa586e87f34bef3bb15431d149ec7aeae0f7d24 gecko-integration-branch: central gecko-reviewers: backout
1 parent 17b7215
README.md
This directory contains tests for the
[Async Cookies API](https://github.com/WICG/cookie-store).
## 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.
![swh spinner](/static/img/swh-spinner.gif)
Computing file changes ...