OK, since I mentioned this problem area as a relative weakness of Pharo in a separate list for the VW non-commercial, I suppose it would be right to close the loop and ask how people get HTTPS working on Pharo. I'm talking about both scenarios, as client and server. The client scenario is calling XMLRPC servers over HTTPS. I did not get this to work out of the box after installing XmlRpcClient libraries, as the underlying Http Client libraries in Pharo do not have SSL support. It seems the preferred answer is to use Apache to proxy the calls to any URL requiring SSL support. I know about Zodiac but could not get it working quickly and just went with VW for developing the first iteration of my integration with multiple XMLRPC APIs. The server scenario involves supporting calls over HTTPS using, say, Aida or Seaside. It's easy in this case to say just let the web server (Apache) handle that, but what if I want to use Swazoo (to keep moving parts to a minimum)? I do most development on Windows, where I usually have IIS installed (for .NET stuff), and that plays nice with absolutely no one. Specifically, I have to be able to support a site that variously accepts HTTP and HTTPS calls, so I'd have to run it on multiple ports, at a minimum. How can I get both scenarios to work in Pharo without involving Apache? -- Bob Calco bob.calco@softcraft-solutions.com