From: Abhishek Lekshmanan Date: Tue, 22 Aug 2017 12:03:01 +0000 (+0200) Subject: doc: rgw: mention the civetweb support for binding to multiple ports X-Git-Tag: v13.0.1~1046^2 X-Git-Url: http://git-server-git.apps.pok.os.sepia.ceph.com/?a=commitdiff_plain;h=01740c6a6c1ae523ac73c24235be0e4cef71e21c;p=ceph.git doc: rgw: mention the civetweb support for binding to multiple ports We support binding multiple ports in civetweb after the upgrade to 1.8, clarify this in the documentation as well Fixes: http://tracker.ceph.com/issues/20942 Signed-off-by: Abhishek Lekshmanan --- diff --git a/doc/install/install-ceph-gateway.rst b/doc/install/install-ceph-gateway.rst index cf599cd2ac8..09fdf921e37 100644 --- a/doc/install/install-ceph-gateway.rst +++ b/doc/install/install-ceph-gateway.rst @@ -159,13 +159,21 @@ CA or intermediate certificates be supplied in one file. Each of these items must be in `pem` form. Because the combined file contains the secret key, it should be protected from unauthorized access. -To configure ssl operation, append ``s`` to the port number. Currently -it is not possible to configure the radosgw to listen on both -http and https, you must pick only one. So:: +To configure ssl operation, append ``s`` to the port number. For eg:: [client.rgw.gateway-node1] rgw_frontends = civetweb port=443s ssl_certificate=/etc/ceph/private/keyandcert.pem +.. versionadded :: Luminous + +Furthermore, civetweb can be made to bind to multiple ports, by separating them +with ``+`` in the configuration. This allows for use cases where both ssl and +non-ssl connections are hosted by a single rgw instance. For eg:: + + [client.rgw.gateway-node1] + rgw_frontends = civetweb port=80+443s ssl_certificate=/etc/ceph/private/keyandcert.pem + + Migrating from Apache to Civetweb ---------------------------------