Storage methods, browser sessions serve 3, phone sessions 0 and computer sessions 3. A method marked not served answers StrategyUnavailable on that kind of session; check the handshake’s capabilities before relying on one.
Storage.getCookies
Browser: served
Phone: not served
Computer: served
The session’s cookies, or those that would be sent to urls. Partitioned cookies carry partitionKey, so setCookies round-trips them.
| Param | Type | Required | Description |
|---|---|---|---|
urls | string[] | No | Only cookies that would be sent to these URLs. Omitted means all. |
| Field | Type | Description |
|---|---|---|
cookies | Cookie[] |
Storage.setCookies
Browser: served
Phone: not served
Computer: served
Set cookies, for example to carry a login from another session.
| Param | Type | Required | Description |
|---|---|---|---|
cookies | Cookie[] | Yes | |
idempotencyKey | string | No | Makes a re-send after a reconnect safe: a repeated key returns the recorded response without acting again. See Idempotency keys. |
{}.
Storage.clearCookies
Browser: served
Phone: not served
Computer: served
Delete every cookie in the session.
| Param | Type | Required | Description |
|---|---|---|---|
idempotencyKey | string | No | Makes a re-send after a reconnect safe: a repeated key returns the recorded response without acting again. See Idempotency keys. |
{}.