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.
32 .. versionadded:: Firefly
34 The ``civetweb`` frontend uses the Civetweb HTTP library, which is a
43 :Description: Sets the listening port number. For SSL-enabled ports, add an
44 ``s`` suffix like ``443s``. To bind a specific IPv4 or IPv6
45 address, use the form ``address:port``. Multiple endpoints
46 can be separated by ``+`` as in ``127.0.0.1:8000+443s``.
54 :Description: Sets the number of threads spawned by Civetweb to handle
55 incoming HTTP connections. This effectively limits the number
56 of concurrent connections that the frontend can service.
59 :Default: ``rgw_thread_pool_size``
62 ``request_timeout_ms``
64 :Description: The amount of time in milliseconds that Civetweb will wait
65 for more incoming data before giving up.
73 :Description: Path to the SSL certificate file used for SSL-enabled ports.
79 A complete list of supported options can be found in the `Civetweb User Manual`_.
85 Some frontend options are generic and supported by all frontends:
89 :Description: A prefix string that is inserted into the URI of all
90 requests. For example, a swift-only frontend could supply
91 a uri prefix of ``/swift``.
97 .. _Civetweb User Manual: https://civetweb.github.io/civetweb/UserManual.html