Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

doc: rgw: mention the civetweb support for binding to multiple ports #17141

Merged
merged 1 commit into from
Sep 5, 2017
Merged

doc: rgw: mention the civetweb support for binding to multiple ports #17141

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
14 changes: 11 additions & 3 deletions doc/install/install-ceph-gateway.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
---------------------------------

Expand Down