<?php

    header('Content-Type: text/plain');

    $response = '';

    $request = xmlrpc_encode_request(
        'public.listEntries', array('id', 'cid')
    );

    $fo = @fsockopen('localhost', 80, $errno, $errstr, 30);
    
    if ($fo) {
        $data = "POST /Testlabor/xmlrpc_server.php HTTP/1.1\r\n"
              . "Host: localhost\r\n"
              . "Content-Length: " . strlen($request) . "\r\n"
              . "Connection: close\r\n\r\n"
              . $request;

        fwrite($fo, $data);
        while(!feof($fo)) {
            $response .= fgets($fo, 128);
        }
        fclose($fo);
        $response = (substr($response, strpos($response, "\r\n\r\n")+4));
        var_dump(xmlrpc_decode($response));
       // echo $response;
    }
    else {
        echo 'Error: Could not connect to server.';
    }

?>

HTTP/1.1 200 OK
Date: Thu, 13 Jul 2006 17:56:15 GMT
Server: Apache/2.0.58 (Win32) SVN/1.3.1 DAV/2
X-Powered-By: PHP/5.1.2
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-15

1e0
<?xml version="1.0" encoding="iso-8859-15"?>
<methodResponse>
<params>
 <param>
  <value>
   <array>
    <data>
     <value>
      <struct>
       <member>
        <name>id</name>
        <value>
         <string>1</string>
        </value>
       </member>
       <member>
        <name>cid</name>
        <value>
         <string>1</string>
        </value>
       </member>
      </struct>
     </value>
    </data>
   </array>
  </value>
 </param>
</params>
</methodResponse>

0

3.6.1 Chunked Transfer Coding
The chunked encoding modifies the body of a message in order to transfer it as a series of chunks, each with its own
size indicator, followed by an OPTIONAL trailer containing entity-header fields. This allows dynamically produced
content to be transferred along with the information necessary for the recipient to verify that it has received the full
message.
Chunked-Body = *chunk
last-chunk
trailer
CRLF
chunk = chunk-size [ chunk-extension ] CRLF
chunk-data CRLF
chunk-size = 1*HEX
last-chunk = 1*("0") [ chunk-extension ] CRLF
chunk-extension= *( ";" chunk-ext-name [ "=" chunk-ext-val ] )
chunk-ext-name = token
chunk-ext-val = token | quoted-string
chunk-data = chunk-size(OCTET)
trailer = *(entity-header CRLF)
The chunk-size field is a string of hex digits indicating the size of the chunk. The chunked encoding is ended by
any chunk whose size is zero, followed by the trailer, which is terminated by an empty line.
The trailer allows the sender to include additional HTTP header fields at the end of the message. The Trailer
header field can be used to indicate which header fields are included in a trailer (see section 14.40).
A server using chunked transfer-coding in a response MUST NOT use the trailer for any header fields unless at least
one of the following is true:
a) the request included a TE header field that indicates “trailers” is acceptable in the transfer-coding of the
response, as described in section 14.39; or,
b) the server is the origin server for the response, the trailer fields consist entirely of optional metadata, and the
recipient could use the message (in a manner acceptable to the origin server) without receiving this
metadata. In other words, the origin server is willing to accept the possibility that the trailer fields might
be silently discarded along the path to the client.
This requirement prevents an interoperability failure when the message is being received by an HTTP/1.1 (or later)
proxy and forwarded to an HTTP/1.0 recipient. It avoids a situation where compliance with the protocol would have
necessitated a possibly infinite buffer on the proxy.
An example process for decoding a Chunked-Body is presented in appendix 19.4.6.
All HTTP/1.1 applications MUST be able to receive and decode the “chunked” transfer-coding, and MUST ignore
chunk-extension extensions they do not understand.