Allow configurable root path for HTTP API

[dhiaayachi]

Describe the solution you'd like

Even though our server API only listens to /namespaces, /cluster, and /system-info, some users may still want that at a deeper level (as opposed to their proxies trimming it off), so allow users to specify a path prefix.

[dhiaayachi]

Thank you for your feature request! We understand the desire for more granular control over the API path prefix. Currently, Temporal only supports the /namespaces, /cluster, and /system-info paths.

As a workaround, you can consider setting up a proxy that would handle the path prefixing before forwarding requests to Temporal. This allows you to maintain your desired API path structure while still utilizing Temporal's core functionalities.

We appreciate your feedback and will consider it for future development.

[dhiaayachi]

Thank you for your feature request!

While we currently don't have the option to specify a path prefix, you can achieve similar functionality by using a proxy server in front of Temporal. The proxy server can handle routing requests to the specific endpoints you're interested in.

Let me know if you have any other questions.

[dhiaayachi]

Thank you for the feature request! We appreciate your suggestion to allow users to specify a path prefix for Temporal's API.

While this feature is not currently available, you can work around it by using a proxy server that removes the path prefix from the request before forwarding it to Temporal. This would allow users to access the API at a deeper level while still ensuring that the server only listens to the /namespaces, /cluster, and /system-info endpoints.

We will keep your feedback in mind for future development.

[dhiaayachi]

Thanks for the feature request! We understand the need for more granular control over the API path prefix. While we don't currently offer a way to directly configure the prefix, you can achieve a similar outcome by using a proxy that modifies the path before it reaches Temporal. This way, the API will still be accessible at the desired path without changing Temporal's configuration.

Link to Temporal Proxy documentation

[dhiaayachi]

Thank you for the feature request! We appreciate the suggestion. Currently, Temporal doesn't support specifying a path prefix for the HTTP API.

You can work around this limitation by using a reverse proxy in front of your Temporal server. The proxy can handle the path prefix and route requests to the correct endpoints on the Temporal server.

Here are some popular reverse proxy options:

• Nginx
• Apache HTTP Server
• HAProxy
• Traefik

These options provide different features and configurations, so you can choose the one that best fits your needs.