Changelog
 2023-07-05
- Improved performance for ranged reads on very large files. Previously ranged reads near the end of very large files would be noticeably slower than ranged reads on smaller files. Performance should now be consistently good independent of filesize.
 2023-06-21
- Multipart ETags are now MD5 hashes.
 2023-06-16
- Fixed a bug where calling GetBucket on a non-existent bucket would return a 500 instead of a 404.
- Improved S3 compatibility for ListObjectsV1, now nextmarker is only set when truncated is true.
- The R2 worker bindings now support parsing conditional headers with multiple etags. These etags can now be strong, weak or a wildcard. Previously the bindings only accepted headers containing a single strong etag.
- S3 putObject now supports sha256 and sha1 checksums. These were already supported by the R2 worker bindings.
- CopyObject in the S3 compatible api now supports Cloudflare specific headers which allow the copy operation to be conditional on the state of the destination object.
 2023-04-01
- GetBucket is now available for use through the Cloudflare API.
- Location hints can now be set when creating a bucket, both through the S3 API, and the dashboard.
 2023-03-16
- The ListParts API has been implemented and is available for use.
- HTTP2 is now enabled by default for new custom domains linked to R2 buckets.
- Object Lifecycles are now available for use.
- Bug fix: Requests to public buckets will now return the Content-Encodingheader for gzip files whenAccept-Encoding: gzipis used.
 2023-01-27
- R2 authentication tokens created via the R2 token page are now scoped to a single account by default.
 2022-12-07
- Fix CORS preflight requests for the S3 API, which allows using the S3 SDK in the browser.
- Passing a range header to the getoperation in the R2 bindings API should now work as expected.
 2022-11-30
- Requests with the header x-amz-acl: public-readare no longer rejected.
- Fixed issues with wildcard CORS rules and presigned URLs.
- Fixed an issue where ListObjectswould time out during delimited listing of unicode-normalized keys.
- S3 API’s PutBucketCorsnow rejects requests with unknown keys in the XML body.
- Signing additional headers no longer breaks CORS preflight requests for presigned URLs.
 2022-11-21
- Fixed a bug in ListObjectswherestartAfterwould skip over objects with keys that have numbers right after thestartAfterprefix.
- Add worker bindings for multipart uploads.
 2022-11-17
- Unconditionally return HTTP 206 on ranged requests to match behavior of other S3 compatible implementations.
- Fixed a CORS bug where AllowedHeadersin the CORS config were being treated case-sensitively.
 2022-11-08
- Copying multipart objects via CopyObjectis re-enabled.
- UploadPartCopyis re-enabled.
 2022-10-28
- Multipart upload part sizes are always expected to be of the same size, but this enforcement is now done when you complete an upload instead of being done very time you upload a part.
- Fixed a performance issue where concurrent multipart part uploads would get rejected.
 2022-10-26
- Fixed ranged reads for multipart objects with part sizes unaligned to 64KiB.
 2022-10-19
- HeadBucketnow sets- x-amz-bucket-regionto- autoin the response.
 2022-10-06
- Temporarily disabled UploadPartCopywhile we investigate an issue.
 2022-09-29
- Fixed a CORS issue where Access-Control-Allow-Headerswas not being set for preflight requests.
 2022-09-28
- Fixed a bug where CORS configuration was not being applied to S3 endpoint.
- No-longer render the Access-Control-Expose-Headersresponse header ifExposeHeaderis not defined.
- Public buckets will no-longer return the Content-Rangeresponse header unless the response is partial.
- Fixed CORS rendering for the S3 HeadObjectoperation.
- Fixed a bug where no matching CORS configuration could result in a 403response.
- Temporarily disable copying objects that were created with multipart uploads.
- Fixed a bug in the Workers bindings where an internal error was being returned for malformed ranged .getrequests.
 2022-09-27
- CORS preflight responses and adding CORS headers for other responses is now implemented for S3 and public buckets. Currently, the only way to configure CORS is via the S3 API.
- Fixup for bindings list truncation to work more correctly when listing keys with custom metadata that have "or when some keys/values contain certain multi-byte UTF-8 values.
- The S3 GetObjectoperation now only returnsContent-Rangein response to a ranged request.
 2022-09-19
- The R2 put()binding options can now be given anonlyIffield, similar toget(), that performs a conditional upload.
- The R2 delete()binding now supports deleting multiple keys at once.
- The R2 put()binding now supports user-specified SHA-1, SHA-256, SHA-384, SHA-512 checksums in options.
- User-specified object checksums will now be available in the R2 get()andhead()bindings response. MD5 is included by default for non-multipart uploaded objects.
 2022-09-06
- The S3 CopyObjectoperation now includesx-amz-version-idandx-amz-copy-source-version-idin the response headers for consistency with other methods.
- The ETagfor multipart files uploaded until shortly after Open Beta uploaded now include the number of parts as a suffix.
 2022-08-17
- The S3 DeleteObjectsoperation no longer trims the space from around the keys before deleting. This would result in files with leading / trailing spaces not being able to be deleted. Additionally, if there was an object with the trimmed key that existed it would be deleted instead. The S3DeleteObjectoperation was not affected by this.
- Fixed presigned URL support for the S3 ListBucketsandListObjectsoperations.
 2022-08-06
- Uploads will automatically infer the Content-Typebased on file body if one is not explicitly set in thePutObjectrequest. This functionality will come to multipart operations in the future.
 2022-07-30
- Fixed S3 conditionals to work properly when provided the LastModifieddate of the last upload, bindings fixes will come in the next release.
- If-Match/- If-None-Matchheaders now support arrays of ETags, Weak ETags and wildcard (- *) as per the HTTP standard and undocumented AWS S3 behavior.
 2022-07-21
- Added dummy implementation of the following operation that mimics
the response that a basic AWS S3 bucket will return when first created: GetBucketAcl.
 2022-07-20
- Added dummy implementations of the following operations that mimic the response that a basic AWS S3 bucket will return when first created: - GetBucketVersioning
- GetBucketLifecycleConfiguration
- GetBucketReplication
- GetBucketTagging
- GetObjectLockConfiguration
 
 2022-07-19
- Fixed an S3 compatibility issue for error responses with MinIO .NET SDK and any other tooling that expects no xmlnsnamespace attribute on the top-levelErrortag.
- List continuation tokens prior to 2022-07-01 are no longer accepted and must be obtained again through a new listoperation.
- The list()binding will now correctly return a smaller limit if too much data would otherwise be returned (previously would return anInternal Error).
 2022-07-14
- Improvements to 500s: we now convert errors, so things that were previously concurrency problems for some operations should now be TooMuchConcurrencyinstead ofInternalError. We’ve also reduced the rate of 500s through internal improvements.
- ListMultipartUploadcorrectly encodes the returned- Keyif the- encoding-typeis specified.
 2022-07-13
- S3 XML documents sent to R2 that have an XML declaration are not rejected with 400 Bad Request/MalformedXML.
- Minor S3 XML compatibility fix impacting Arq Backup on Windows only (not the Mac version). Response now contains XML declaration tag prefix and the xmlns attribute is present on all top-level tags in the response.
- Beta ListMultipartUploadssupport.
 2022-07-06
- Support the r2_list_honor_includecompat flag coming up in an upcoming runtime release (default behavior as of 2022-07-14 compat date). Without that compat flag/date, list will continue to function implicitly asinclude: ['httpMetadata', 'customMetadata']regardless of what you specify.
- cf-create-bucket-if-missingcan be set on a- PutObject/- CreateMultipartUploadrequest to implicitly create the bucket if it does not exist.
- Fix S3 compatibility with MinIO client spec non-compliant XML for publishing multipart uploads. Any leading and trailing quotes in CompleteMultipartUploadare now optional and ignored as it seems to be the actual non-standard behavior AWS implements.
 2022-07-01
- Unsupported search parameters to ListObjects/ListObjectsV2are now rejected with501 Not Implemented.
- Fixes for Listing:- Fix listing behavior when the number of files within a folder exceeds the limit (you’d end up seeing a CommonPrefix for that large folder N times where N = number of children within the CommonPrefix / limit).
- Fix corner case where listing could cause objects with sharing the base name of a "folder" to be skipped.
- Fix listing over some files that shared a certain common prefix.
 
- DeleteObjectscan now handle 1000 objects at a time.
- S3 CreateBucketrequest can specifyx-amz-bucket-object-lock-enabledwith a value offalseand not have the requested rejected with aNotImplementederror. A value oftruewill continue to be rejected as R2 does not yet support object locks.
 2022-06-17
- Fixed a regression for some clients when using an empty delimiter.
- Added support for S3 pre-signed URLs.
 2022-06-16
- Fixed a regression in the S3 API UploadPartoperation whereTooMuchConcurrency&NoSuchUploaderrors were being returned asNoSuchBucket.
 2022-06-13
- Fixed a bug with the S3 API ListObjectsV2operation not returning empty folder/s as common prefixes when using delimiters.
- The S3 API ListObjectsV2KeyCountparameter now correctly returns the sum of keys and common prefixes rather than just the keys.
- Invalid cursors for list operations no longer fail with an InternalErrorand now return the appropriate error message.
 2022-06-10
- The ContinuationTokenfield is now correctly returned in the response if provided in a S3 APIListObjectsV2request.
- Fixed a bug where the S3 API AbortMultipartUploadoperation threw an error when called multiple times.
 2022-05-27
- Fixed a bug where the S3 API’s PutObjector the.put()binding could fail but still show the bucket upload as successful.
- If conditional headers are provided to S3 API UploadObjectorCreateMultipartUploadoperations, and the object exists, a412 Precondition Failedstatus code will be returned if these checks are not met.
 2022-05-20
- Fixed a bug when Accept-Encodingwas being used inSignedHeaderswhen sending requests to the S3 API would result in aSignatureDoesNotMatchresponse.
 2022-05-17
- Fixed a bug where requests to the S3 API were not handling non-encoded parameters used for the authorization signature.
- Fixed a bug where requests to the S3 API where number-like keys were being parsed as numbers instead of strings.
 2022-05-16
- Add support for S3 virtual-hosted style paths, such as <BUCKET>.<ACCOUNT_ID>.r2.cloudflarestorage.cominstead of path-based routing (<ACCOUNT_ID>.r2.cloudflarestorage.com/<BUCKET>).
- Implemented GetBucketLocationfor compatibility with external tools, this will always return aLocationConstraintofauto.
 2022-05-06
- S3 API GetObjectranges are now inclusive (bytes=0-0will correctly return the first byte).
- S3 API GetObjectpartial reads return the proper206 Partial Contentresponse code.
- Copying from a non-existent key (or from a non-existent bucket) to another bucket now returns the proper NoSuchKey/NoSuchBucketresponse.
- The S3 API now returns the proper Content-Type: application/xmlresponse header on relevant endpoints.
- Multipart uploads now have a -Nsuffix on the etag representing the number of parts the file was published with.
- UploadPartand- UploadPartCopynow return proper error messages, such as- TooMuchConcurrencyor- NoSuchUpload, instead of ‘internal error’.
- UploadPartcan now be sent a 0-length part.
 2022-05-05
- When using the S3 API, an empty string and us-east-1will now alias to theautoregion for compatibility with external tools.
- GetBucketEncryption,- PutBucketEncryptionand- DeleteBucketEncrypotionare now supported (the only supported value currently is- AES256).
- Unsupported operations are explicitly rejected as unimplemented rather than implicitly converting them into ListObjectsV2/PutBucket/DeleteBucketrespectively.
- S3 API CompleteMultipartUploadsrequests are now properly escaped.
 2022-05-03
- Pagination cursors are no longer returned when the keys in a bucket is the same as the MaxKeysargument.
- The S3 API ListBucketsoperation now acceptscf-max-keys,cf-start-afterandcf-continuation-tokenheaders behave the same as the respective URL parameters.
- The S3 API ListBucketsandListObjectsendpoints now allowper_pageto be 0.
- The S3 API CopyObjectsource parameter now requires a leading slash.
- The S3 API CopyObjectoperation now returns aNoSuchBucketerror when copying to a non-existent bucket instead of an internal error.
- Enforce the requirement for autoin SigV4 signing and theCreateBucketLocationConstraintparameter.
- The S3 API CreateBucketoperation now returns the properlocationresponse header.
 2022-04-14
- The S3 API now supports unchunked signed payloads.
- Fixed .put()for the Workers R2 bindings.
- Fixed a regression where key names were not properly decoded when using the S3 API.
- Fixed a bug where deleting an object and then another object which is a prefix of the first could result in errors.
- The S3 API DeleteObjectsoperation no longer returns an error even though an object has been deleted in some cases.
- Fixed a bug where startAfterandcontinuationTokenwere not working in list operations.
- The S3 API ListObjectsoperation now correctly rendersPrefix,Delimiter,StartAfterandMaxKeysin the response.
- The S3 API ListObjectsV2now correctly honors theencoding-typeparameter.
- The S3 API PutObjectoperation now works withPOSTrequests fors3cmdcompatibility.
 2022-04-04
- The S3 API DeleteObjectsrequest now properly returns aMalformedXMLerror instead ofInternalErrorwhen provided with more than 128 keys.