This page explains the different request endpoints (URIs) used to access Cloud Storage through the XML API. The endpoint to use depends on the operation performed and the type of request.
Note: The Cloud Storage URIs described in this document are subject to change.
URIs for standard requests
Unless noted otherwise below, you can use either of the following URLs to access buckets and objects:
Both forms support secure sockets layer (SSL) encryption, which means you can use either HTTP or HTTPS. For a list of XML API requests that can use these URIs, see Reference Methods.
Google Cloud Storage also provides dedicated XML API endpoints just for uploads or downloads.
For uploads, you can use either of:
For downloads, you can use either of:
Both endpoints support secure sockets layer (SSL) encryption.
The download endpoint only supports downloading data while the upload endpoint only supports uploading data. You may see a small performance benefit from using these dedicated endpoints when transferring large amounts of data.
For connections through a proxy, see the FAQ entry on proxies for recommended practices.
URI for CNAME redirects
When using a CNAME alias to redirect requests, you must use a special URI to access Cloud Storage. A CNAME redirect is a special DNS record that lets you use a URL from your own domain to access a resource (bucket and object) in Cloud Storage without revealing the Cloud Storage URI. To do this, you must use the following URI in the host name portion of your CNAME record:
For example, assume your domain is
example.com and you want to make travel maps
available to your customers. You could create a bucket in Cloud Storage called
travel-maps.example.com, and then create a CNAME record in DNS that redirects requests
travel-maps.example.com to the Cloud Storage URI. To do this, publish the
following CNAME record in DNS:
travel-maps.example.com CNAME c.storage.googleapis.com.
Your customers can then use the following URL to access a map of Paris:
When creating a bucket that will be used to serve resources for redirect requests, your bucket name must conform to standard DNS naming conventions. See Bucket Name Requirements for more information. Related to this, for an example of configuring a bucket as a web site see Configuring a Bucket as a Website.
URI for authenticated browser downloads
The Cloud Storage authentication and authorization models support authenticated browser downloads for users who do not have Cloud Storage accounts. Authenticated browser downloads use cookie-based Google account authentication in conjunction with Google account-based ACLs. To download an object using cookie-based authentication you must use the following URL:
We strongly recommend using HTTPS for authenticated browser downloads, but both HTTP and HTTPS are supported. For more information about authenticated browser downloads, see Cookie-based Authentication under Authentication.