From 8442c43209508131613339082861ef70ff2690f7 Mon Sep 17 00:00:00 2001 From: Wouter van Os Date: Sun, 31 Jan 2021 15:10:03 +0100 Subject: [PATCH] doc: Update wording for S3 path-only requirement --- doc/030_preparing_a_new_repo.rst | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/doc/030_preparing_a_new_repo.rst b/doc/030_preparing_a_new_repo.rst index 49f8a3e25..a2762e04e 100644 --- a/doc/030_preparing_a_new_repo.rst +++ b/doc/030_preparing_a_new_repo.rst @@ -238,11 +238,12 @@ after the bucket name like this: 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 like this: ``s3:http://server:port/bucket_name``. - -.. note:: Currently, restic only supports defining the `path-style URLs `__. Virtual-hosted–style URLs, where the bucket name is in the - hostname itself (like ``bucket_name.s3.us-west-2.amazonaws.com``), - is not supported. It should be written in the path-style URL instead, - for example ``s3.us-west-2.amazonaws.com/bucket_name``. + +.. note:: restic expects `path-style URLs `__ + like for example ````s3.us-west-2.amazonaws.com/bucket_name``. + Virtual-hosted–style URLs like ``bucket_name.s3.us-west-2.amazonaws.com``, + 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 ``ListObjectsV2`` API, most notably Ceph versions before v14.2.5. On these