Hi @futuregerald,
Thanks for your check. Unfortunately, the error is still persist. To reproduce it, I do nothing in particular, just type the address https://www.moovetech.io in a browser. You can even produce it with a curl command like this:
curl -H 'Accept-Language: en-US,en;q=0.5' -L -v -s https://www.moovetech.io 1> /dev/null
and its output (in my computer, based in Paris, France):
* Rebuilt URL to: https://www.moovetech.io/
* Trying 167.99.129.42...
* TCP_NODELAY set
* Connected to www.moovetech.io (167.99.129.42) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
} [222 bytes data]
* TLSv1.2 (IN), TLS handshake, Server hello (2):
{ [102 bytes data]
* TLSv1.2 (IN), TLS handshake, Certificate (11):
{ [2570 bytes data]
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
{ [300 bytes data]
* TLSv1.2 (IN), TLS handshake, Server finished (14):
{ [4 bytes data]
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
} [37 bytes data]
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
} [1 bytes data]
* TLSv1.2 (OUT), TLS handshake, Finished (20):
} [16 bytes data]
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
{ [1 bytes data]
* TLSv1.2 (IN), TLS handshake, Finished (20):
{ [16 bytes data]
* SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
* ALPN, server accepted to use h2
* Server certificate:
* subject: CN=moovetech.io
* start date: Jul 19 01:29:38 2019 GMT
* expire date: Oct 17 01:29:38 2019 GMT
* subjectAltName: host "www.moovetech.io" matched cert's "www.moovetech.io"
* issuer: C=US; O=Let's Encrypt; CN=Let's Encrypt Authority X3
* SSL certificate verify ok.
* 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 0x7f837b006600)
> GET / HTTP/2
> Host: www.moovetech.io
> User-Agent: curl/7.54.0
> Accept: */*
> Accept-Language: en-US,en;q=0.5
>
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 302
< cache-control: public, max-age=0, must-revalidate
< content-length: 20
< content-type: text/plain; charset=utf-8
< date: Fri, 09 Aug 2019 05:40:40 GMT
< location: /fr/
< age: 266477
< server: Netlify
< x-nf-request-id: de5a6584-b422-4c83-9209-91b71677ec39-6055060
<
* Ignoring the response-body
{ [20 bytes data]
* Connection #0 to host www.moovetech.io left intact
* Issue another request to this URL: 'https://www.moovetech.io/fr/'
* Found bundle for host www.moovetech.io: 0x7f837a516bf0 [can multiplex]
* Re-using existing connection! (#0) with host www.moovetech.io
* Connected to www.moovetech.io (167.99.129.42) port 443 (#0)
* Using Stream ID: 3 (easy handle 0x7f837b006600)
> GET /fr/ HTTP/2
> Host: www.moovetech.io
> User-Agent: curl/7.54.0
> Accept: */*
> Accept-Language: en-US,en;q=0.5
>
< HTTP/2 200
< cache-control: public, max-age=0, must-revalidate
< content-type: text/html; charset=UTF-8
< date: Fri, 09 Aug 2019 20:31:36 GMT
< etag: "9141d92a19fb4522b219e2cbb6649bda-ssl"
< strict-transport-security: max-age=31536000
< age: 213021
< content-length: 1353472
< server: Netlify
< x-nf-request-id: de5a6584-b422-4c83-9209-91b71677ec39-6055083
<
{ [16384 bytes data]
* Connection #0 to host www.moovetech.io left intact
Its Netlify ID is: de5a6584-b422-4c83-9209-91b71677ec39-6055060
Other test with my browser: de5a6584-b422-4c83-9209-91b71677ec39-6101910
Hope it helps.
