From b467489b002ab4e1fc855b8daa1cdad1a79026d6 Mon Sep 17 00:00:00 2001 From: Casey Bodley Date: Mon, 24 Feb 2025 16:50:39 -0500 Subject: [PATCH] doc/rgw: clarify path-style vs virtual-hosted-style access instead of referring to "vhost-style", copy the "path-style" and "virtual-hosted-style" language from https://docs.aws.amazon.com/AmazonS3/latest/userguide/VirtualHosting.html expand the FQDN acronym to avoid potential confusion "The second method is deprecated by AWS" had incorrectly referred to the vhost-style method - clarify that it refers to path-style access Signed-off-by: Casey Bodley (cherry picked from commit c61c314ed6482cc26cf69ed7e2af4af20bebd676) --- doc/radosgw/s3/commons.rst | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/radosgw/s3/commons.rst b/doc/radosgw/s3/commons.rst index 91cf2e02005..5047f8fdecc 100644 --- a/doc/radosgw/s3/commons.rst +++ b/doc/radosgw/s3/commons.rst @@ -7,19 +7,19 @@ Bucket and Host Name -------------------- -There are two different modes of accessing buckets. The first method identifies -the bucket as the top-level directory in the URI:: +There are two different modes of accessing buckets: path-style and virtual-hosted-style. +Path-style requests identify the bucket as the top-level directory of the request's path:: GET /mybucket HTTP/1.1 Host: cname.domain.com -Most S3 clients nowadays rely on vhost-style access. The desired bucket is -indicated by a DNS FQDN. For example:: +Most S3 clients default to virtual-hosted-style access, where the bucket name is instead +indicated as part of the fully-qualified domain name:: GET / HTTP/1.1 Host: mybucket.cname.domain.com -The second method is deprecated by AWS. See the `Amazon S3 Path Deprecation +Path-style access is deprecated by AWS. See the `Amazon S3 Path Deprecation Plan`_ for more information. To configure virtual hosted buckets, you can either set ``rgw_dns_name = -- 2.47.3