If you wanted to use HTTP instead of HTTPS, you would change the URL to https:// and also the Port number in the --resolve the argument would change from 443 to 80

Note we have included the --insecure flag in this command as it skips cURL’s default behaviour of validating the SSL certificate presented by your server. If you have a valid certificate installed, you can remove this flag.

The --resolve the flag allows you to neatly force a request to a specific IP address, but some older versions of cURL don’t support it. If absolutely necessary, you can use a different way of doing this.

curl (versions 7.21.2 and older)

curl --silent --verbose //123.123.123.123/example-url/here --header "Host: example.com"

The resulting output from cURL will show you the full HTTP response. Including headers direct from your origin server’s IP address – removing Cloudflare from the equation entirely. Therefore if you still see the issue you’re experiencing with this output. You can be sure you’ll need to investigate what is happening on your server. As the issue is not caused by Cloudflare. If it’s not obvious what the next step is from here, contacting your hosting provider for assistance is the best way forward.