Edi, basically, the HTTP server forces the client to authenticate itself using a client certificate. I believe RFC2246 describes the process, see http://www.ietf.org/rfc/rfc2246.txt. The patches at http://web.kepibu.org/code/lisp/cl+ssl/ which add client certificate support have already been incorporated into CL+SSL, so it should be relatively easy to add support to Drakma, perhaps by adding client-ssl-certificate and client-ssl-key keywords to http-request and then passing the args to cl+ssl:make-ssl-client-stream in request.lisp. Unless I have missed something and there is a way to do this already, I will experiment and send you a patch.
Cheers. Kevin Edi Weitz wrote: > On Tue, Apr 14, 2009 at 12:28 AM, Kevin Raison <rai...@chatsubo.net> wrote: >> Hello. I am using a site for credit card authorization that requires me >> to send my personal SSL certificate with any POST. I don't see anything >> in the Drakma documentation about how to go about this; is it possible? >> I would rather not use curl, but it does have the -E option that >> allows for sending certificates to the remote host. Any help would be >> appreciated! > > I have to admit that I'm not familiar with how this is done in > general. Is there an RFC for this or can you point me to some > documentation? > > Thanks, > Edi. > > _______________________________________________ > drakma-devel mailing list > drakma-devel@common-lisp.net > http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-devel > _______________________________________________ drakma-devel mailing list drakma-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/drakma-devel