2
2
mirror of https://github.com/octoleo/restic.git synced 2024-05-29 07:00:49 +00:00

doc: Update wording for S3 path-only requirement

This commit is contained in:
Wouter van Os 2021-01-31 15:10:03 +01:00 committed by GitHub
parent b5972f184c
commit 8442c43209
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -238,11 +238,12 @@ after the bucket name like this:
For an S3-compatible server that is not Amazon (like Minio, see below), For an S3-compatible server that is not Amazon (like Minio, see below),
or is only available via HTTP, you can specify the URL to the server or is only available via HTTP, you can specify the URL to the server
like this: ``s3:http://server:port/bucket_name``. like this: ``s3:http://server:port/bucket_name``.
.. note:: Currently, restic only supports defining the `path-style URLs <https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro>`__. Virtual-hostedstyle URLs, where the bucket name is in the .. note:: restic expects `path-style URLs <https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingBucket.html#access-bucket-intro>`__
hostname itself (like ``bucket_name.s3.us-west-2.amazonaws.com``), like for example ````s3.us-west-2.amazonaws.com/bucket_name``.
is not supported. It should be written in the path-style URL instead, Virtual-hostedstyle URLs like ``bucket_name.s3.us-west-2.amazonaws.com``,
for example ``s3.us-west-2.amazonaws.com/bucket_name``. where the bucket name is part of the hostname are not supported. These must
be converted to path-style URLs instead, for example ``s3.us-west-2.amazonaws.com/bucket_name``.
.. note:: Certain S3-compatible servers do not properly implement the .. note:: Certain S3-compatible servers do not properly implement the
``ListObjectsV2`` API, most notably Ceph versions before v14.2.5. On these ``ListObjectsV2`` API, most notably Ceph versions before v14.2.5. On these