Skip to main content
Hi everyone,

 

Regarding the end of TLS 1.0 support, I made a few tests in our sandbox.

 

There seems to be one problem left : the recording of Web-To-Case forms.

 

Actually, we do not use the default configuration for Web-To-Case : instead of just retrieving the HTML code in Salesforce config, we changed the destination of this form in the HTML form tag so that it is redirected to a custom PHP script.

 

The PHP code we use looks like this :

 

 

// Retrieving information

$content = "&orgid=" . $orgid;

$content .= "&name=" . $name;

$content .= "&company=" . $company;

[...]

// Setting header

$header = "POST /servlet/servlet.WebToCase?encoding=UTF-8 HTTP/1.0\r\n";

$header .= "Content-Type: application/x-www-form-urlencoded\r\n";

$header .= "Host: csXX.salesforce.com\r\n";

$header .= "Content-Length: " . strlen($content) . "\r\n\r\n";

// Sending to Salesforce

$fp = fsockopen('csXX.salesforce.com', 80, $errno, $errstr, 30);

if ($fp) {

fputs($fp, $header.$content);

while (!feof($fp)) {

$result = fgets($fp, 1024);

}

}

 

Also, I do not have every piece of information I would like to have : the PHP code and adaptation was written by the person who held the job before me, so no clue as to why it has been done that way instead of another. To be fair, it worked pretty well until now, but the end of TLS 1.0 support is about to change that.

 

That being said, I do not know what to do in order to make our Web-To-Case compatible with TLS 1.1/1.2.

 

Any assistance would be greatly appreciated.

 

Thanks a lot
6 件の回答
  1. 2017年9月4日 14:30
    I see, we have had a similar issue with web-to-lead but our confusion was a silly one as we didnt use the correct org id during the testing as we have few sandboxes. Also our live org and sanbox are very different from config point of view so its worth double checking the config. Can you do a run in LIVE ? just 1 test case ? see if the outcome is the same.

     

    Regards

     

    Artur