Using CORS in private buckets
Because browsers are specifically mandated to strip user-headers from CORS requests, it is not possible to use the AUTHORIZATION header in download requests from private buckets when those requests come from a browser.
Use the alternative authentication method of appending the authentication string to the download URL. For example, to download the file helloworld.html from a public bucket publichello the url might be:
https://f000.backblaze2.com/files/publichello/helloworld.html
To download a similar file from a bucket privatehello might be:
https://f000.backblaze2.com/files/privatehello/helloworld.html? Authorization= 3_20181021181348_ 1654aeb9046d1bcdd60dff3c_ 06314b74a8fc99f72def5a18c1b3c87ab35f329c_ 000_ 20181030221348_ 0000_ dnld
Please note: Although web standards are to ignore case in the headers, URLS are case sensitive. Authorization must have the first letter capitalized, and the remainder in lower case.
Articles in this section
- Object Lock FAQs
- Bunny Integration Quick Start Guide
- Guide for using Fastly Compute @ Edge with Backblaze B2
- SSE Command Line and API Examples
- Does the B2 S3 Compatible API support Pre-Signed URLs?
- Using CORS in private buckets
- How does the startFileName parameter work on the b2_list file_names API?
- Does B2 require a SHA-1 hash to be provided with an upload?