HTTP Interface

The HTTP interface lets you use ClickHouse on any platform from any programming language. We use it for working from Java and Perl, as well as shell scripts. In other departments, the HTTP interface is used from Perl, Python, and Go. The HTTP interface is more limited than the native interface, but it has better compatibility.

By default, clickhouse-server listens for HTTP on port 8123 (this can be changed in the config).

If you make a GET / request without parameters, it returns 200 response code and the string which defined in http_server_default_response default value “Ok.” (with a line feed at the end)

  1. $ curl 'http://localhost:8123/'
  2. Ok.

Use GET /ping request in health-check scripts. This handler always returns “Ok.” (with a line feed at the end). Available from version 18.12.13.

  1. $ curl 'http://localhost:8123/ping'
  2. Ok.

Send the request as a URL ‘query’ parameter, or as a POST. Or send the beginning of the query in the ‘query’ parameter, and the rest in the POST (we’ll explain later why this is necessary). The size of the URL is limited to 16 KB, so keep this in mind when sending large queries.

If successful, you receive the 200 response code and the result in the response body.
If an error occurs, you receive the 500 response code and an error description text in the response body.

When using the GET method, ‘readonly’ is set. In other words, for queries that modify data, you can only use the POST method. You can send the query itself either in the POST body or in the URL parameter.

Examples:

  1. $ curl 'http://localhost:8123/?query=SELECT%201'
  2. 1
  4. $ wget -nv -O- 'http://localhost:8123/?query=SELECT 1'
  5. 1
  7. $ echo -ne 'GET /?query=SELECT%201 HTTP/1.0\r\n\r\n' | nc localhost 8123
  8. HTTP/1.0 200 OK
  9. Date: Wed, 27 Nov 2019 10:30:18 GMT
  10. Connection: Close
  11. Content-Type: text/tab-separated-values; charset=UTF-8
  12. X-ClickHouse-Server-Display-Name: clickhouse.ru-central1.internal
  13. X-ClickHouse-Query-Id: 5abe861c-239c-467f-b955-8a201abb8b7f
  14. X-ClickHouse-Summary: {"read_rows":"0","read_bytes":"0","written_rows":"0","written_bytes":"0","total_rows_to_read":"0"}
  16. 1

As you can see, curl is somewhat inconvenient in that spaces must be URL escaped.
Although wget escapes everything itself, we don’t recommend using it because it doesn’t work well over HTTP 1.1 when using keep-alive and Transfer-Encoding: chunked.

  1. $ echo 'SELECT 1' | curl 'http://localhost:8123/' --data-binary @-
  2. 1
  4. $ echo 'SELECT 1' | curl 'http://localhost:8123/?query=' --data-binary @-
  5. 1
  7. $ echo '1' | curl 'http://localhost:8123/?query=SELECT' --data-binary @-
  8. 1

If part of the query is sent in the parameter, and part in the POST, a line feed is inserted between these two data parts.
Example (this won’t work):

  1. $ echo 'ECT 1' | curl 'http://localhost:8123/?query=SEL' --data-binary @-
  2. Code: 59, e.displayText() = DB::Exception: Syntax error: failed at position 0: SEL
  3. ECT 1
  4. , expected One of: SHOW TABLES, SHOW DATABASES, SELECT, INSERT, CREATE, ATTACH, RENAME, DROP, DETACH, USE, SET, OPTIMIZE., e.what() = DB::Exception

By default, data is returned in TabSeparated format (for more information, see the “Formats” section).

You use the FORMAT clause of the query to request any other format.

Also, you can use the ‘default_format’ URL parameter or the ‘X-ClickHouse-Format’ header to specify a default format other than TabSeparated.

  1. $ echo 'SELECT 1 FORMAT Pretty' | curl 'http://localhost:8123/?' --data-binary @-
  2. ┏━━━┓
  3. ┃ 1 ┃
  4. ┡━━━┩
  5. │ 1 │
  6. └───┘

The POST method of transmitting data is necessary for INSERT queries. In this case, you can write the beginning of the query in the URL parameter, and use POST to pass the data to insert. The data to insert could be, for example, a tab-separated dump from MySQL. In this way, the INSERT query replaces LOAD DATA LOCAL INFILE from MySQL.

Examples: Creating a table:

  1. $ echo 'CREATE TABLE t (a UInt8) ENGINE = Memory' | curl 'http://localhost:8123/' --data-binary @-

Using the familiar INSERT query for data insertion:

  1. $ echo 'INSERT INTO t VALUES (1),(2),(3)' | curl 'http://localhost:8123/' --data-binary @-

Data can be sent separately from the query:

  1. $ echo '(4),(5),(6)' | curl 'http://localhost:8123/?query=INSERT%20INTO%20t%20VALUES' --data-binary @-

You can specify any data format. The ‘Values’ format is the same as what is used when writing INSERT INTO t VALUES:

  1. $ echo '(7),(8),(9)' | curl 'http://localhost:8123/?query=INSERT%20INTO%20t%20FORMAT%20Values' --data-binary @-

To insert data from a tab-separated dump, specify the corresponding format:

  1. $ echo -ne '10\n11\n12\n' | curl 'http://localhost:8123/?query=INSERT%20INTO%20t%20FORMAT%20TabSeparated' --data-binary @-

Reading the table contents. Data is output in random order due to parallel query processing:

  1. $ curl 'http://localhost:8123/?query=SELECT%20a%20FROM%20t'
  2. 7
  3. 8
  4. 9
  5. 10
  6. 11
  7. 12
  8. 1
  9. 2
  10. 3
  11. 4
  12. 5
  13. 6

Deleting the table.

  1. $ echo 'DROP TABLE t' | curl 'http://localhost:8123/' --data-binary @-

For successful requests that don’t return a data table, an empty response body is returned.

Compression

You can use compression to reduce network traffic when transmitting a large amount of data or for creating dumps that are immediately compressed.

You can use the internal ClickHouse compression format when transmitting data. The compressed data has a non-standard format, and you need clickhouse-compressor program to work with it. It is installed with the clickhouse-client package. To increase the efficiency of data insertion, you can disable server-side checksum verification by using the http_native_compression_disable_checksumming_on_decompress setting.

If you specify compress=1 in the URL, the server will compress the data it sends to you. If you specify decompress=1 in the URL, the server will decompress the data which you pass in the POST method.

You can also choose to use HTTP compression. ClickHouse supports the following compression methods:

  • gzip
  • br
  • deflate
  • xz

To send a compressed POST request, append the request header Content-Encoding: compression_method.
In order for ClickHouse to compress the response, enable compression with enable_http_compression setting and append Accept-Encoding: compression_method header to the request. You can configure the data compression level in the http_zlib_compression_level setting for all compression methods.

Note

Some HTTP clients might decompress data from the server by default (with gzip and deflate) and you might get decompressed data even if you use the compression settings correctly.

Examples

  1. # Sending compressed data to the server
  2. $ echo "SELECT 1" | gzip -c | \
  3.   curl -sS --data-binary @- -H 'Content-Encoding: gzip' 'http://localhost:8123/'
  1. # Receiving compressed data from the server
  2. $ curl -vsS "http://localhost:8123/?enable_http_compression=1" \
  3.     -H 'Accept-Encoding: gzip' --output result.gz -d 'SELECT number FROM system.numbers LIMIT 3'
  4. $ zcat result.gz
  5. 0
  6. 1
  7. 2

Default Database

You can use the ‘database’ URL parameter or the ‘X-ClickHouse-Database’ header to specify the default database.

  1. $ echo 'SELECT number FROM numbers LIMIT 10' | curl 'http://localhost:8123/?database=system' --data-binary @-
  2. 0
  3. 1
  4. 2
  5. 3
  6. 4
  7. 5
  8. 6
  9. 7
  10. 8
  11. 9

By default, the database that is registered in the server settings is used as the default database. By default, this is the database called ‘default’. Alternatively, you can always specify the database using a dot before the table name.

The username and password can be indicated in one of three ways:

  1. Using HTTP Basic Authentication. Example:
  1. $ echo 'SELECT 1' | curl 'http://user:[email protected]:8123/' -d @-
  1. In the ‘user’ and ‘password’ URL parameters. Example:
  1. $ echo 'SELECT 1' | curl 'http://localhost:8123/?user=user&password=password' -d @-
  1. Using ‘X-ClickHouse-User’ and ‘X-ClickHouse-Key’ headers. Example:
  1. $ echo 'SELECT 1' | curl -H 'X-ClickHouse-User: user' -H 'X-ClickHouse-Key: password' 'http://localhost:8123/' -d @-

If the user name is not specified, the default name is used. If the password is not specified, the empty password is used.
You can also use the URL parameters to specify any settings for processing a single query or entire profiles of settings. Example:http://localhost:8123/?profile=web&max_rows_to_read=1000000000&query=SELECT+1

For more information, see the Settings section.

  1. $ echo 'SELECT number FROM system.numbers LIMIT 10' | curl 'http://localhost:8123/?' --data-binary @-
  2. 0
  3. 1
  4. 2
  5. 3
  6. 4
  7. 5
  8. 6
  9. 7
  10. 8
  11. 9

For information about other parameters, see the section “SET”.

Similarly, you can use ClickHouse sessions in the HTTP protocol. To do this, you need to add the session_id GET parameter to the request. You can use any string as the session ID. By default, the session is terminated after 60 seconds of inactivity. To change this timeout, modify the default_session_timeout setting in the server configuration, or add the session_timeout GET parameter to the request. To check the session status, use the session_check=1 parameter. Only one query at a time can be executed within a single session.

You can receive information about the progress of a query in X-ClickHouse-Progress response headers. To do this, enable send_progress_in_http_headers. Example of the header sequence:

  1. X-ClickHouse-Progress: {"read_rows":"2752512","read_bytes":"240570816","total_rows_to_read":"8880128"}
  2. X-ClickHouse-Progress: {"read_rows":"5439488","read_bytes":"482285394","total_rows_to_read":"8880128"}
  3. X-ClickHouse-Progress: {"read_rows":"8783786","read_bytes":"819092887","total_rows_to_read":"8880128"}

Possible header fields:

  • read_rows — Number of rows read.
  • read_bytes — Volume of data read in bytes.
  • total_rows_to_read — Total number of rows to be read.
  • written_rows — Number of rows written.
  • written_bytes — Volume of data written in bytes.

Running requests don’t stop automatically if the HTTP connection is lost. Parsing and data formatting are performed on the server-side, and using the network might be ineffective.
The optional ‘query_id’ parameter can be passed as the query ID (any string). For more information, see the section “Settings, replace_running_query”.

The optional ‘quota_key’ parameter can be passed as the quota key (any string). For more information, see the section “Quotas”.

The HTTP interface allows passing external data (external temporary tables) for querying. For more information, see the section “External data for query processing”.

Response Buffering

You can enable response buffering on the server-side. The buffer_size and wait_end_of_query URL parameters are provided for this purpose.

buffer_size determines the number of bytes in the result to buffer in the server memory. If a result body is larger than this threshold, the buffer is written to the HTTP channel, and the remaining data is sent directly to the HTTP channel.

To ensure that the entire response is buffered, set wait_end_of_query=1. In this case, the data that is not stored in memory will be buffered in a temporary server file.

Example:

  1. $ curl -sS 'http://localhost:8123/?max_result_bytes=4000000&buffer_size=3000000&wait_end_of_query=1' -d 'SELECT toUInt8(number) FROM system.numbers LIMIT 9000000 FORMAT RowBinary'

Use buffering to avoid situations where a query processing error occurred after the response code and HTTP headers were sent to the client. In this situation, an error message is written at the end of the response body, and on the client-side, the error can only be detected at the parsing stage.

Queries with Parameters

You can create a query with parameters and pass values for them from the corresponding HTTP request parameters. For more information, see Queries with Parameters for CLI.

Example

  1. $ curl -sS "<address>?param_id=2&param_phrase=test" -d "SELECT * FROM table WHERE int_column = {id:UInt8} and string_column = {phrase:String}"

Predefined HTTP Interface

ClickHouse supports specific queries through the HTTP interface. For example, you can write data to a table as follows:

  1. $ echo '(4),(5),(6)' | curl 'http://localhost:8123/?query=INSERT%20INTO%20t%20VALUES' --data-binary @-

ClickHouse also supports Predefined HTTP Interface which can help you more easily integrate with third-party tools like Prometheus exporter.

Example:

  • First of all, add this section to server configuration file:
  1. <http_handlers>
  2.     <rule>
  3.         <url>/predefined_query</url>
  4.         <methods>POST,GET</methods>
  5.         <handler>
  6.             <type>predefined_query_handler</type>
  7.             <query>SELECT * FROM system.metrics LIMIT 5 FORMAT Template SETTINGS format_template_resultset = 'prometheus_template_output_format_resultset', format_template_row = 'prometheus_template_output_format_row', format_template_rows_between_delimiter = '\n'</query>
  8.         </handler>
  9.     </rule>
  10.     <rule>...</rule>
  11.     <rule>...</rule>
  12. </http_handlers>
  • You can now request the URL directly for data in the Prometheus format:
  1. $ curl -v 'http://localhost:8123/predefined_query'
  2. *   Trying ::1...
  3. * Connected to localhost (::1) port 8123 (#0)
  4. > GET /predefined_query HTTP/1.1
  5. > Host: localhost:8123
  6. > User-Agent: curl/7.47.0
  7. > Accept: */*
  8. >
  9. < HTTP/1.1 200 OK
  10. < Date: Tue, 28 Apr 2020 08:52:56 GMT
  11. < Connection: Keep-Alive
  12. < Content-Type: text/plain; charset=UTF-8
  13. < X-ClickHouse-Server-Display-Name: i-mloy5trc
  14. < Transfer-Encoding: chunked
  15. < X-ClickHouse-Query-Id: 96fe0052-01e6-43ce-b12a-6b7370de6e8a
  16. < X-ClickHouse-Format: Template
  17. < X-ClickHouse-Timezone: Asia/Shanghai
  18. < Keep-Alive: timeout=3
  19. < X-ClickHouse-Summary: {"read_rows":"0","read_bytes":"0","written_rows":"0","written_bytes":"0","total_rows_to_read":"0"}
  20. <
  21. # HELP "Query" "Number of executing queries"
  22. # TYPE "Query" counter
  23. "Query" 1
  25. # HELP "Merge" "Number of executing background merges"
  26. # TYPE "Merge" counter
  27. "Merge" 0
  29. # HELP "PartMutation" "Number of mutations (ALTER DELETE/UPDATE)"
  30. # TYPE "PartMutation" counter
  31. "PartMutation" 0
  33. # HELP "ReplicatedFetch" "Number of data parts being fetched from replica"
  34. # TYPE "ReplicatedFetch" counter
  35. "ReplicatedFetch" 0
  37. # HELP "ReplicatedSend" "Number of data parts being sent to replicas"
  38. # TYPE "ReplicatedSend" counter
  39. "ReplicatedSend" 0
  41. * Connection #0 to host localhost left intact
  43. * Connection #0 to host localhost left intact

As you can see from the example if http_handlers is configured in the config.xml file and http_handlers can contain many rules. ClickHouse will match the HTTP requests received to the predefined type in rule and the first matched runs the handler. Then ClickHouse will execute the corresponding predefined query if the match is successful.

Now rule can configure method, headers, url, handler:
- method is responsible for matching the method part of the HTTP request. method fully conforms to the definition of method in the HTTP protocol. It is an optional configuration. If it is not defined in the configuration file, it does not match the method portion of the HTTP request.

  • url is responsible for matching the URL part of the HTTP request. It is compatible with RE2’s regular expressions. It is an optional configuration. If it is not defined in the configuration file, it does not match the URL portion of the HTTP request.

  • headers are responsible for matching the header part of the HTTP request. It is compatible with RE2’s regular expressions. It is an optional configuration. If it is not defined in the configuration file, it does not match the header portion of the HTTP request.

  • handler contains the main processing part. Now handler can configure type, status, content_type, response_content, query, query_param_name.
    type currently supports three types: predefined_query_handler, dynamic_query_handler, static.

    • query — use with predefined_query_handler type, executes query when the handler is called.

    • query_param_name — use with dynamic_query_handler type, extracts and executes the value corresponding to the query_param_name value in HTTP request params.

    • status — use with static type, response status code.

    • content_type — use with static type, response content-type.

    • response_content — use with static type, response content sent to client, when using the prefix ‘file://’ or ‘config://’, find the content from the file or configuration sends to client.

Next are the configuration methods for different type.

predefined_query_handler

predefined_query_handler supports setting Settings and query_params values. You can configure query in the type of predefined_query_handler.

query value is a predefined query of predefined_query_handler, which is executed by ClickHouse when an HTTP request is matched and the result of the query is returned. It is a must configuration.

The following example defines the values of max_threads and max_alter_threads settings, then queries the system table to check whether these settings were set successfully.

Example:

  1. <http_handlers>
  2.     <rule>
  3.         <url><![CDATA[/query_param_with_url/\w+/(?P<name_1>[^/]+)(/(?P<name_2>[^/]+))?]]></url>
  4.         <method>GET</method>
  5.         <headers>
  6.             <XXX>TEST_HEADER_VALUE</XXX>
  7.             <PARAMS_XXX><![CDATA[(?P<name_1>[^/]+)(/(?P<name_2>[^/]+))?]]></PARAMS_XXX>
  8.         </headers>
  9.         <handler>
  10.             <type>predefined_query_handler</type>
  11.             <query>SELECT value FROM system.settings WHERE name = {name_1:String}</query>
  12.             <query>SELECT name, value FROM system.settings WHERE name = {name_2:String}</query>
  13.         </handler>
  14.     </rule>
  15. </http_handlers>
  1. $ curl -H 'XXX:TEST_HEADER_VALUE' -H 'PARAMS_XXX:max_threads' 'http://localhost:8123/query_param_with_url/1/max_threads/max_alter_threads?max_threads=1&max_alter_threads=2'
  2. 1
  3. max_alter_threads   2

caution

In one predefined_query_handler only supports one query of an insert type.

dynamic_query_handler

In dynamic_query_handler, the query is written in the form of param of the HTTP request. The difference is that in predefined_query_handler, the query is written in the configuration file. You can configure query_param_name in dynamic_query_handler.

ClickHouse extracts and executes the value corresponding to the query_param_name value in the URL of the HTTP request. The default value of query_param_name is /query . It is an optional configuration. If there is no definition in the configuration file, the param is not passed in.

To experiment with this functionality, the example defines the values of max_threads and max_alter_threads and queries whether the settings were set successfully.

Example:

  1. <http_handlers>
  2.     <rule>
  3.     <headers>
  4.         <XXX>TEST_HEADER_VALUE_DYNAMIC</XXX>    </headers>
  5.     <handler>
  6.         <type>dynamic_query_handler</type>
  7.         <query_param_name>query_param</query_param_name>
  8.     </handler>
  9.     </rule>
  10. </http_handlers>
  1. $ curl  -H 'XXX:TEST_HEADER_VALUE_DYNAMIC'  'http://localhost:8123/own?max_threads=1&max_alter_threads=2&param_name_1=max_threads&param_name_2=max_alter_threads&query_param=SELECT%20name,value%20FROM%20system.settings%20where%20name%20=%20%7Bname_1:String%7D%20OR%20name%20=%20%7Bname_2:String%7D'
  2. max_threads 1
  3. max_alter_threads   2

static

static can return content_type, status and response_content. response_content can return the specified content.

Example:

Return a message.

  1. <http_handlers>
  2.         <rule>
  3.             <methods>GET</methods>
  4.             <headers><XXX>xxx</XXX></headers>
  5.             <url>/hi</url>
  6.             <handler>
  7.                 <type>static</type>
  8.                 <status>402</status>
  9.                 <content_type>text/html; charset=UTF-8</content_type>
  10.                 <response_content>Say Hi!</response_content>
  11.             </handler>
  12.         </rule>
  13. <http_handlers>
  1. $ curl -vv  -H 'XXX:xxx' 'http://localhost:8123/hi'
  2. *   Trying ::1...
  3. * Connected to localhost (::1) port 8123 (#0)
  4. > GET /hi HTTP/1.1
  5. > Host: localhost:8123
  6. > User-Agent: curl/7.47.0
  7. > Accept: */*
  8. > XXX:xxx
  9. >
  10. < HTTP/1.1 402 Payment Required
  11. < Date: Wed, 29 Apr 2020 03:51:26 GMT
  12. < Connection: Keep-Alive
  13. < Content-Type: text/html; charset=UTF-8
  14. < Transfer-Encoding: chunked
  15. < Keep-Alive: timeout=3
  16. < X-ClickHouse-Summary: {"read_rows":"0","read_bytes":"0","written_rows":"0","written_bytes":"0","total_rows_to_read":"0"}
  17. <
  18. * Connection #0 to host localhost left intact
  19. Say Hi!%

Find the content from the configuration send to client.

  1. <get_config_static_handler><![CDATA[<html ng-app="SMI2"><head><base href="http://ui.tabix.io/"></head><body><div ui-view="" class="content-ui"></div><script src="http://loader.tabix.io/master.js"></script></body></html>]]></get_config_static_handler>
  3. <http_handlers>
  4.         <rule>
  5.             <methods>GET</methods>
  6.             <headers><XXX>xxx</XXX></headers>
  7.             <url>/get_config_static_handler</url>
  8.             <handler>
  9.                 <type>static</type>
  10.                 <response_content>config://get_config_static_handler</response_content>
  11.             </handler>
  12.         </rule>
  13. </http_handlers>
  1. $ curl -v  -H 'XXX:xxx' 'http://localhost:8123/get_config_static_handler'
  2. *   Trying ::1...
  3. * Connected to localhost (::1) port 8123 (#0)
  4. > GET /get_config_static_handler HTTP/1.1
  5. > Host: localhost:8123
  6. > User-Agent: curl/7.47.0
  7. > Accept: */*
  8. > XXX:xxx
  9. >
  10. < HTTP/1.1 200 OK
  11. < Date: Wed, 29 Apr 2020 04:01:24 GMT
  12. < Connection: Keep-Alive
  13. < Content-Type: text/plain; charset=UTF-8
  14. < Transfer-Encoding: chunked
  15. < Keep-Alive: timeout=3
  16. < X-ClickHouse-Summary: {"read_rows":"0","read_bytes":"0","written_rows":"0","written_bytes":"0","total_rows_to_read":"0"}
  17. <
  18. * Connection #0 to host localhost left intact
  19. <html ng-app="SMI2"><head><base href="http://ui.tabix.io/"></head><body><div ui-view="" class="content-ui"></div><script src="http://loader.tabix.io/master.js"></script></body></html>%

Find the content from the file send to client.

  1. <http_handlers>
  2.         <rule>
  3.             <methods>GET</methods>
  4.             <headers><XXX>xxx</XXX></headers>
  5.             <url>/get_absolute_path_static_handler</url>
  6.             <handler>
  7.                 <type>static</type>
  8.                 <content_type>text/html; charset=UTF-8</content_type>
  9.                 <response_content>file:///absolute_path_file.html</response_content>
  10.             </handler>
  11.         </rule>
  12.         <rule>
  13.             <methods>GET</methods>
  14.             <headers><XXX>xxx</XXX></headers>
  15.             <url>/get_relative_path_static_handler</url>
  16.             <handler>
  17.                 <type>static</type>
  18.                 <content_type>text/html; charset=UTF-8</content_type>
  19.                 <response_content>file://./relative_path_file.html</response_content>
  20.             </handler>
  21.         </rule>
  22. </http_handlers>
  1. $ user_files_path='/var/lib/clickhouse/user_files'
  2. $ sudo echo "<html><body>Relative Path File</body></html>" > $user_files_path/relative_path_file.html
  3. $ sudo echo "<html><body>Absolute Path File</body></html>" > $user_files_path/absolute_path_file.html
  4. $ curl -vv -H 'XXX:xxx' 'http://localhost:8123/get_absolute_path_static_handler'
  5. *   Trying ::1...
  6. * Connected to localhost (::1) port 8123 (#0)
  7. > GET /get_absolute_path_static_handler HTTP/1.1
  8. > Host: localhost:8123
  9. > User-Agent: curl/7.47.0
  10. > Accept: */*
  11. > XXX:xxx
  12. >
  13. < HTTP/1.1 200 OK
  14. < Date: Wed, 29 Apr 2020 04:18:16 GMT
  15. < Connection: Keep-Alive
  16. < Content-Type: text/html; charset=UTF-8
  17. < Transfer-Encoding: chunked
  18. < Keep-Alive: timeout=3
  19. < X-ClickHouse-Summary: {"read_rows":"0","read_bytes":"0","written_rows":"0","written_bytes":"0","total_rows_to_read":"0"}
  20. <
  21. <html><body>Absolute Path File</body></html>
  22. * Connection #0 to host localhost left intact
  23. $ curl -vv -H 'XXX:xxx' 'http://localhost:8123/get_relative_path_static_handler'
  24. *   Trying ::1...
  25. * Connected to localhost (::1) port 8123 (#0)
  26. > GET /get_relative_path_static_handler HTTP/1.1
  27. > Host: localhost:8123
  28. > User-Agent: curl/7.47.0
  29. > Accept: */*
  30. > XXX:xxx
  31. >
  32. < HTTP/1.1 200 OK
  33. < Date: Wed, 29 Apr 2020 04:18:31 GMT
  34. < Connection: Keep-Alive
  35. < Content-Type: text/html; charset=UTF-8
  36. < Transfer-Encoding: chunked
  37. < Keep-Alive: timeout=3
  38. < X-ClickHouse-Summary: {"read_rows":"0","read_bytes":"0","written_rows":"0","written_bytes":"0","total_rows_to_read":"0"}
  39. <
  40. <html><body>Relative Path File</body></html>
  41. * Connection #0 to host localhost left intact

Original article