5 ms·

Curl wasn’t able to normalise ip adresses till this commit [0] [0] https://github.com/curl/curl/commit/56a037cc0ad1b2a770d0c08d3d09dee1ce600f0f https://github.

Curl wasn’t able to normalise ip adresses till this commit [0] [0] https://github.com/curl/curl/commit/56a037cc0ad1b2a770d0c08d3d09dee1ce600f0f https://github.com/curl/curl/commit/56a037cc0ad1b2a770d0c08d...

judge2020 4y ago
Indeed - so while it's hitting Cloudflare, the 1.1.1.1 IPs are all technically vhosts for `cloudflare-dns.com`, so a good `host` header in the request is required to reach it. For this reason, you could use a CNAME setup[0] and instead of using CNAMEs for proxied subdomains, you input 1.1.1.1 A records in your authoritative dns, and everything on Cloudflare's side will still see your hostname in the host header / SNI, and your website will load. 0: https://developers.cloudflare.com/dns/zone-setups/partial-setup/ https://developers.cloudflare.com/dns/zone-setups/partial-se...