7 The Ceph Object Gateway supports two embedded HTTP frontend libraries
8 that can be configured with ``rgw_frontends``.
13 .. versionadded:: Luminous
15 The ``beast`` frontend uses the Boost.Beast library for HTTP parsing
16 and the Boost.Asio library for asynchronous network i/o.
23 :Description: Sets the listening port number. Can be specified multiple
24 times as in ``port=80 port=8000``.
32 :Description: Sets the listening address in the form ``address[:port]``,
33 where the address is an IPv4 address string in dotted decimal
34 form, or an IPv6 address in hexadecimal notation. The
35 optional port defaults to 80. Can be specified multiple times
36 as in ``endpoint=::1 endpoint=192.168.0.100:8000``.
45 .. versionadded:: Firefly
47 The ``civetweb`` frontend uses the Civetweb HTTP library, which is a
56 :Description: Sets the listening port number. For SSL-enabled ports, add an
57 ``s`` suffix like ``443s``. To bind a specific IPv4 or IPv6
58 address, use the form ``address:port``. Multiple endpoints
59 can either be separated by ``+`` as in ``127.0.0.1:8000+443s``,
60 or by providing multiple options as in ``port=8000 port=443s``.
68 :Description: Sets the number of threads spawned by Civetweb to handle
69 incoming HTTP connections. This effectively limits the number
70 of concurrent connections that the frontend can service.
73 :Default: ``rgw_thread_pool_size``
76 ``request_timeout_ms``
78 :Description: The amount of time in milliseconds that Civetweb will wait
79 for more incoming data before giving up.
87 :Description: Path to the SSL certificate file used for SSL-enabled ports.
93 A complete list of supported options can be found in the `Civetweb User Manual`_.
99 Some frontend options are generic and supported by all frontends:
103 :Description: A prefix string that is inserted into the URI of all
104 requests. For example, a swift-only frontend could supply
105 a uri prefix of ``/swift``.
111 .. _Civetweb User Manual: https://civetweb.github.io/civetweb/UserManual.html