For those willing to use HTTP/2, please be aware that it is **only possible if your server is configured with SSL certificate**. Therefore, you will see how to launch a MeiliSearch server with SSL. This tutorial gives a short introduction to do it locally, but you can as well do the same thing on a remote server. First of all, you need the [binary of MeiliSearch](https://docs.meilisearch.com/reference/features/installation.html), or you can also use docker. In the latter case, it is necessary to pass the parameters using environment variables and the SSL certificates via a volume. A tool to generate SSL certificates is also required. In this How To, you will use [mkcert](https://github.com/FiloSottile/mkcert). However, if on a remote server, you can also use certbot or certificates signed by a Certificate Authority. Then, use `curl` to do requests. It is a simple way to specify that you want to send HTTP/2 requests by using the `--http2` option. ## Try to use HTTP/2 without SSL Start by running the binary. ``` ./meilisearch ``` And then, send a request. ``` curl -kvs --http2 --request GET 'http://localhost:7700/indexes' ``` You will get the following answer from the server: ``` * Trying ::1... * TCP_NODELAY set * Connection failed * connect to ::1 port 7700 failed: Connection refused * Trying 127.0.0.1... * TCP_NODELAY set * Connected to localhost (127.0.0.1) port 7700 (#0) > GET /indexes HTTP/1.1 > Host: localhost:7700 > User-Agent: curl/7.64.1 > Accept: */* > Connection: Upgrade, HTTP2-Settings > Upgrade: h2c > HTTP2-Settings: AAMAAABkAARAAAAAAAIAAAAA > < HTTP/1.1 200 OK < content-length: 2 < content-type: application/json < date: Fri, 17 Jul 2020 11:01:02 GMT < * Connection #0 to host localhost left intact []* Closing connection 0 ``` You can see on line `> Connection: Upgrade, HTTP2-Settings` that the server tries to upgrade to HTTP/2, but is unsuccessful. The answer `< HTTP/1.1 200 OK` indicates that the server still uses HTTP/1. ## Try to use HTTP/2 with SSL This time, start by generating the SSL certificates. mkcert creates two files: `127.0.0.1.pem` and `127.0.0.1-key.pem`. ``` mkcert '127.0.0.1' ``` Then, use the certificate and the key to configure MeiliSearch with SSL. ``` ./meilisearch --ssl-cert-path ./127.0.0.1.pem --ssl-key-path ./127.0.0.1-key.pem ``` Next, make the same request as above but change `http://` to `https://`. ``` curl -kvs --http2 --request GET 'https://localhost:7700/indexes' ``` You will get the following answer from the server: ``` * Trying ::1... * TCP_NODELAY set * Connection failed * connect to ::1 port 7700 failed: Connection refused * Trying 127.0.0.1... * TCP_NODELAY set * Connected to localhost (127.0.0.1) port 7700 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/cert.pem CApath: none * TLSv1.2 (OUT), TLS handshake, Client hello (1): * TLSv1.2 (IN), TLS handshake, Server hello (2): * TLSv1.2 (IN), TLS handshake, Certificate (11): * TLSv1.2 (IN), TLS handshake, Server key exchange (12): * TLSv1.2 (IN), TLS handshake, Server finished (14): * TLSv1.2 (OUT), TLS handshake, Client key exchange (16): * TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.2 (OUT), TLS handshake, Finished (20): * TLSv1.2 (IN), TLS change cipher, Change cipher spec (1): * TLSv1.2 (IN), TLS handshake, Finished (20): * SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384 * ALPN, server accepted to use h2 * Server certificate: * subject: O=mkcert development certificate; OU=quentindequelen@s-iMac (Quentin de Quelen) * start date: Jun 1 00:00:00 2019 GMT * expire date: Jul 17 10:38:53 2030 GMT * issuer: O=mkcert development CA; OU=quentindequelen@s-iMac (Quentin de Quelen); CN=mkcert quentindequelen@s-iMac (Quentin de Quelen) * SSL certificate verify result: unable to get local issuer certificate (20), continuing anyway. * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) * Copying HTTP/2 data in stream buffer to connection buffer after upgrade: len=0 * Using Stream ID: 1 (easy handle 0x7ff601009200) > GET /indexes HTTP/2 > Host: localhost:7700 > User-Agent: curl/7.64.1 > Accept: */* > * Connection state changed (MAX_CONCURRENT_STREAMS == 4294967295)! < HTTP/2 200 < content-length: 2 < content-type: application/json < date: Fri, 17 Jul 2020 11:06:27 GMT < * Connection #0 to host localhost left intact []* Closing connection 0 ``` You can see that the server now supports HTTP/2. ``` * Using HTTP2, server supports multi-use * Connection state changed (HTTP/2 confirmed) ``` The server successfully receives HTTP/2 requests. ``` < HTTP/2 200 ```

qdequele

How to use HTTP/2 and SSL with MeiliSearch

Join Our Newsletter. No Spam, Only the good stuff.