To create a sample access token for testing, use theOAuth 2.0 playground.

Note: If your requests are being routed through a proxy, you might need to check with your network administrator to ensure that requiredAuthorization headers are not stripped out by the proxy. Without theAuthorization header, you receive aMissingSecurityHeader error and your request is rejected. For more information about accessing Cloud Storage through a proxy server, see theTroubleshooting topic.

For additional details, see thespecification.

When appearing in a response, theContent-Range header indicates the range of bytes being returned as a result of a request that included aRange header.

When included as part of aresumable upload request,Content-Range is used to query for the current position of the upload or as an indicator of the starting point of the block of data being uploaded in the current request.

Byte ranges are inclusive; that is,bytes 0-999 represent the first 1000 bytes in a file or object.

For additional details, particularly regarding download responses, see thespecification.

This header specifies the encoding of a message body in a request.

For additional details, see thespecification.

This is required for POST and PUT commands associated with uploading objects and granting permissions; however, this command can alternatively be included in the body of the request instead of as a header (for more information, seeObjects: insert). When making the initial request of aresumable upload that also includes metadata, use the Content-Type header to specify the metadata's data type.

For additional details, see thespecification.

ETag: "39a59594290b0f9a30662a56d695b71d"

ETag: "-CKicn4fknbUCEAE="

This header is currently supported forGET requests. This header is supported for all resources, including buckets, objects and ACLs. If the ETag you specify with this header is the same as the ETag for the requested resource, then the request proceeds normally. If the ETag you specify with this header is different from the ETag for the requested resource, then the request fails and Cloud Storage returns a412 Precondition Failed error code.

For additional details, see thespecification.

This header is currently supported forGET requests. This header is supported for all resources, including buckets, objects and ACLs. If the ETag you specify with this header is different than the ETag for the requested resource, then the request proceeds normally. If the ETag you specify with this header is the same as the ETag of the requested resource, then the request fails and Cloud Storage returns a304 Not Modified status code.

For additional details, see thespecification.

Thelocation header is used for several purposes:

• In response to initiating a resumable upload it provides you with a session URI for a resumable upload operation.
• In response to aCookie-based authentication request it provides you with a unique web origin response URL for the request.
• In response to a JSON API download request made at a URL other than `www.googleapis.com/download` it provides a redirect to the JSON API URL where the download can be made.

For additional details, see thespecification.

When included as a header in a request for object data, only the specified range of bytes for the object gets returned, which is useful when downloading an object in parallel requests or when resuming an interrupted download. Multiple byte ranges in a single request are not accepted, and incertain circumstances theRange request header is ignored.

When returned as part of a response associated with a resumable upload,Range indicates the number of bytes currently uploaded. You can subsequently use this information tocontinue the upload.

Byte ranges are inclusive. For example,bytes=0-999 represent the first 1000 bytes in a file or object. For more information about this header, see thespecification.

This header specifies if the message body of a request or response has been chunked. If it is, content is received or served in a series of chunks, with the final chunk having a length of zero. If you specifyTransfer-Encoding: Chunked, you don't need to specify aContent-Length. This can be useful if you don't know the length of the message body in advance, such as when performing a streaming upload.

For more details about Transfer-Encodings, see thespecification. For more details about chunked transfer encoding, see thespecification.

X-Goog-Custom-Audit-User: user ID test 1

X-Goog-Custom-Audit-Job: test-job-id-here

X-Goog-Custom-Audit-Justification: Removed customer identity record at customer request

The project specified in the header is billed for charges associated with the request. This header is used, for example, when making requests to buckets that haveRequester Pays enabled.

Generally, JSON requests that require a project ID should supply one in the request URL with theuserProject parameter instead of with theX-Goog-User-Project header.

Data format for the response.

• Valid values:json,media
• Default value:json

• Name of the JavaScript callback function that handles the response.
• Used in JavaScriptJSON-P requests.

• For more information, see thepartial response documentation.
• Use for better performance.

Returns response with indentations and line breaks.

• Returns the response in a human-readable format iftrue.
• Default value:true.
• When this isfalse, it can reduce the response payload size, which might lead to better performance in some environments.

• Lets you enforce per-user quotas from a server-side application even in cases when the user's IP address is unknown. This can occur, for example, with applications that run cron jobs on App Engine on a user's behalf.
• You can choose any arbitrary string that uniquely identifies a user, but it is limited to 40 characters.
• Learn more aboutCapping API usage.

• Required for requests to buckets that haveRequester Pays enabled.