Skip to content

Commit abdefd2

Browse files
authored
Merge pull request ceph#61984 from cbodley/wip-doc-rgw-path-style
doc/rgw: clarify path-style vs virtual-hosted-style access Reviewed-by: Zac Dover <[email protected]>
2 parents e68b801 + c61c314 commit abdefd2

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

doc/radosgw/s3/commons.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -7,19 +7,19 @@
77

88
Bucket and Host Name
99
--------------------
10-
There are two different modes of accessing buckets. The first method identifies
11-
the bucket as the top-level directory in the URI::
10+
There are two different modes of accessing buckets: path-style and virtual-hosted-style.
11+
Path-style requests identify the bucket as the top-level directory of the request's path::
1212

1313
GET /mybucket HTTP/1.1
1414
Host: cname.domain.com
1515

16-
Most S3 clients nowadays rely on vhost-style access. The desired bucket is
17-
indicated by a DNS FQDN. For example::
16+
Most S3 clients default to virtual-hosted-style access, where the bucket name is instead
17+
indicated as part of the fully-qualified domain name::
1818

1919
GET / HTTP/1.1
2020
Host: mybucket.cname.domain.com
2121

22-
The second method is deprecated by AWS. See the `Amazon S3 Path Deprecation
22+
Path-style access is deprecated by AWS. See the `Amazon S3 Path Deprecation
2323
Plan`_ for more information.
2424

2525
To configure virtual hosted buckets, you can either set ``rgw_dns_name =

0 commit comments

Comments
 (0)