demo · v133

Storage Access Headers

Pick a scenario and build the exact HTTP exchange Chrome 133+ uses to negotiate cross-site storage access via headers rather than the JS API. Then probe the live Storage Access state on this page.

Origin trial / flag in Chrome 133. Enable chrome://flags/#storage-access-headers to see Sec-Fetch-Storage-Access in real requests.

request (browser -> server)


      

      

        
response (server -> browser)

        

      

    


    

      
document.hasStorageAccess()
-

      
requestStorageAccess()
-

    


    
checking support...

  


  

    
the headers


// Browser -> server (Chrome 133+ on a SAA-eligible request):
Sec-Fetch-Storage-Access: active

// Server -> browser:
Activate-Storage-Access: load   // grant storage on the loaded resource
// or
Activate-Storage-Access: retry; allowed-origin="https://a.example"
// or
Vary: Sec-Fetch-Storage-Access

  


  

    
see also