[RESOLVED] fsockopen() problems.

stevesweetland

ok.

doing lots of stuff thats new to me, and getting very confused.

i have a class set up which is going to be an api payment system, using hsbc.

i have a function.

here it is (in essence)

$theserverip = "xx.xx.xx.xx";
$theurl = "ssl://www.theurl.com";
$theport = 443;

$fp = @fsockopen($theserverip,$theport, $errno, $errstr, 30);
if (!$fp){
	print "<h1>$errstr ($errno)</h1>\n";
} else {
	$out = "POST $theurl HTTP/1.0\r\n";
	$out .= "Host: ".$theserverip."\r\n";
	$out .= "User-Agent: PHP Script\r\n";
	$out .= "Content-type: text/xml\r\n";
	$out .= "Content-length: ".strlen($this->cppData)."\r\n\r\n";
	$out .= "Connection: close";
	$out .= $this->cppData."\r\n";
	$out .= "\r\n";

fwrite($fp, $out);
while (!feof($fp)){
	$this->cppResponse = fgets($fp, 4096);
};

fclose($fp);

$this->ProcessReponse();
};

currently, im getting a 110 error (timed out).

was wondering if you could help me debug this a bit, because if i swap the settings over to even get, lets say, google... id expect to get SOME kind of html reponse.

it was giving me this error once, not sure what i did to stop it, but its not doing it currently.

Warning: fsockopen(): php_hostconnect: connect failed

stevesweetland

ok. i got the result i wanted by setting $theserverip... NOT to be an ip address, but to be a url in the style

ssl://www.theurl.com

(yes, it had to be 'ssl').
now however, when im getting the text response, im getting this at the top of the response...

HTTP/1.1 200 OK
Server: CCE_XMLIC/1.0
Connection: close
Content-Type: text/xml
Content-Length: 804

also.. on the end, i see this

is there an easy way to these annoyances out?

stevesweetland

in case you care... im receiving xml in response

bradgrafelman

Wouldn't using [man]cURL/man be easier?

Anyway, to separate headers from the content, you might try:

$data = array_slice(explode("\r\n\r\n", $data), 1);

MarkR

Don't use the @ operator for anything.

Rather than using fsockopen, consider using fopen(), that has its own http implementation - see the documentation about how the HTTP (/HTTPS) wrappers work. This is more standard than curl.

You can also achieve POSTs with fopen using the HTTP wrapper, see the documentation for more details.

Try getting the URL from the shell (e.g. with wget) from your development / production server (whichever it's not working on). Ensure with your network admin that it's possible to route traffic to that host.

Mark