# cross-origin-storage

Cross-Origin Storage is a proposed web-platform content-addressable cache and JavaScript API for sharing large, byte-identical resources across permitted origins using cryptographic hashes.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Storage Access API

DevFeed: [Storage Access API](<https://devfeed.tech/articles/storage-access-api-89153.md>)

Original publisher: [Read original article](<https://specification.website/spec/privacy/storage-access-api/>)

Author: Joost de Valk

Published: 2026-07-05T10:00:00Z

Content type: tutorial

Language: en

Sources: [The Website Specification](<https://devfeed.tech/sources/the-website-specification.md>)

Topics: [cross-origin-storage](<https://devfeed.tech/topics/cross-origin-storage.md>), [Single sign-on (SSO)](<https://devfeed.tech/topics/sso.md>), [API](<https://devfeed.tech/topics/api.md>)

Tags: [browser](<https://devfeed.tech/tags/browser.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [cross](<https://devfeed.tech/tags/cross.md>), [optional](<https://devfeed.tech/tags/optional.md>), [privacy](<https://devfeed.tech/tags/privacy.md>), [request](<https://devfeed.tech/tags/request.md>)

### AI overview

The Storage Access API lets embedded cross-site content request access to its unpartitioned cookies and storage after a user gesture. This tutorial explains when to use it, the browser and iframe requirements, cookie settings, common mistakes, and ways to verify the flow. It presents the API as a privacy-preserving option for legitimate cases such as federated sign-in and embedded account widgets.

### Source excerpt

As browsers partition and block third-party cookies, embedded cross-site content uses the Storage Access API to request its own cookies behind a user gesture -- instead of asking visitors to switch off tracking protection.

## How cookie tossing attacks led GitHub Pages to move to github.io

DevFeed: [How cookie tossing attacks led GitHub Pages to move to github.io](<https://devfeed.tech/articles/yummy-cookies-across-domains-70218.md>)

Original publisher: [Read original article](<https://github.blog/engineering/infrastructure/yummy-cookies-across-domains/>)

Author: Vicent Martí

Published: 2013-04-10T01:30:07Z

Content type: article

Language: en

Sources: [GitHub Blog](<https://devfeed.tech/sources/github-engineering.md>), [GitHub Engineering](<https://devfeed.tech/sources/github.md>)

Topics: [frontend security](<https://devfeed.tech/topics/frontend-security.md>), [Cookies](<https://devfeed.tech/topics/cookies.md>), [cross-origin-storage](<https://devfeed.tech/topics/cross-origin-storage.md>), [GitHub Pages](<https://devfeed.tech/topics/github-pages.md>)

Tags: [chrome](<https://devfeed.tech/tags/chrome.md>), [cookies](<https://devfeed.tech/tags/cookies.md>), [csrf](<https://devfeed.tech/tags/csrf.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [firefox](<https://devfeed.tech/tags/firefox.md>), [github](<https://devfeed.tech/tags/github.md>), [github-pages](<https://devfeed.tech/tags/github-pages.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [phishing](<https://devfeed.tech/tags/phishing.md>)

### AI overview

GitHub describes how hosting user content on subdomains of github.com enabled cookie tossing attacks against session cookies. The article explains server-side mitigations, including clearing duplicate or encoded cookies, and why browser cookie limits made some attacks impossible to block reliably. GitHub moved Pages to github.io to isolate user content from its main domain and reduce phishing and cross-domain cookie risks.

### Source excerpt

Last Friday we announced and performed a migration of all GitHub Pages to their own github.io domain. This was a long-planned migration, with the specific goal of mitigating phishing attacks...