Sockets and client certificate

Using sockets in RPGLE to send an HTTP request to a remote HTTP server has long 
been standard fare.
Using SSL sockets proved a little more difficult with much thanks to some 
sample RPGLE code from Barbara Morris a couple of years ago.

It is also clear how to embed base64 encoded authentication details into the 
HTTP header for connection to sites that require Basic Authentication. But does 
anyone know how to accomodate a site that requires a client certificate for 
authentication.
I did a brief google search for RFCs on this but they prove to be tiresome.

I would like to think that it's as simple as knowing the correct HTTP 
directives to embed the header and then just copy in the client certificate 
directly from where it is stored on the IFS but that may be wishful thinking.
It would be also be nice to be able to dump a communication trace for such a 
request but it is unfortunately unreadable since it is encrypted. I presume 
that would also be the case for some tool that might expose the header when 
using a browser to connect.

Finding info on this stuff seems like looking for a needle in a haystack.
Can anyone help?

Peter  
This correspondence is for the named person's use only.  It may contain 
confidential or legally privileged information, or both. No confidentiality or 
privilege is waived or lost by any mistransmission. If you receive this 
correspondence in error, please immediately delete it from your system and 
notify the sender. You must not disclose, copy or rely on any part of this 
correspondence if you are not the intended recipient. Any views expressed in 
this message are those of the individual sender, except where the sender 
expressly, and with authority, states them to be the views of Baycorp 
Advantage.If you need assistance, please contact Baycorp Advantage on either :- 
        Australia 133124 or New Zealand +64 9 356 5800