“ERROR! Connection is using HTTP/1.0 protocol. HTTP/1.1 - will return an HTTP 400 response with the following text in the body: HTTPS – will return an HTTP 400 response with the following text in the body: On failure: One of the following errors will occur depending on what your system does not support: On success: A successful connection to will return an HTTP 200 response with the following text in the body: “PayPal_Connection_OK” In that file, copy the following code in to the content of that page:Ĭurl_setopt($ch, CURLOPT_RETURNTRANSFER, 1).Next, create a file called test.php in your site’s root folder.FTP or sFTP work best, but if you have an online file manager that will work fine as well. First, you’ll need access to your site’s files.All we need to do is add a simple test file to our site and check the results. The dubious nature of these “failed” warnings notwithstanding, it’s actually not very hard to check and see if your current server supports these protocols. They can tell you what versions of TLS are enabled for your SSL certificate, but cannot verify that the site itself is functioning properly using TLS 1.2, and they also cannot verify that HTTP/1.1 is supported. *Note: it’s not actually possible to enter in your URL to test for TLS support in a third-party website.
If you’re here, you more than likely received a letter or warning from PayPal or your credit card provider that you failed a test or otherwise need to verify support of these things. With the upcoming changes to PCI compliance and the whole credit-card industry, it’s important to ensure that your SSL encryption supports TLS 1.2 and HTTP/1.1.
0 kommentar(er)
