http_allow_path_requests
Allow the HTTP interface to route path-style requests (such as/my_db/my_table.csv) to the query handler.
This flag gates the routing decision only, which is made before the request is authenticated, so it cannot depend on a per-user setting. After routing, the per-user settings http_allow_database_as_path, http_allow_table_as_file, and http_allow_filters_as_path control whether the routed path is actually interpreted for the authenticated user. When this flag is off, unknown paths return a plain 404.
Enabled by default. Set it to 0 to restore the previous behavior, in which every path that is not a configured handler returns 404.
Example
http_handlers
Allows using custom HTTP handlers. To add a new http handler simply add a new<rule>.
Rules are checked from top to bottom as defined,
and the first match will run the handler.
The following settings can be configured by sub-tags:
handler contains the following settings, which can be configured by sub-tags:
Along with a list of rules, you can specify
<defaults/> which specifies to enable all the default handlers.
Example:
http_options_response
Used to add headers to the response in anOPTIONS HTTP request.
The OPTIONS method is used when making CORS preflight requests.
For more information, see OPTIONS.
Example:
http_server_default_response
The page that is shown by default when you access the ClickHouse HTTP(s) server. The default value is “Ok.” (with a line feed at the end)- Default:
"Ok.\n"
https://tabix.io/ when accessing http://localhost: http_port.