wcf - SOAP API HTTPS - Connecting with Classic ASP

Question

I know there are plenty of discussions relating to connecting a classic ASP client to a SOAP web service, but I'm interesting in connecting to a HTTPS enabled SOAP service.

We have an existing SOAP Web service written in WCF and it works great...for .NET clients. We've had a request from a new customer, "We use classic ASP - how do we connect to your Web Service API?" I didn't have a clue where to start, and it started to dawn on me that I had no idea what the structure of the actual SOAP messages are.

I've seen the examples of classic ASP chatting to SOAP web services on the web, but none which exchange messages over HTTPS. We're using message level security on the WCF bindings.

Is this a lost cause - does WS-Security prevent classic ASP from interfacing with a HTTPS SOAP Service?

Thanks in advance.

Answer 1

Option 1: tell your client what year it is, and suggest that there are costs associated with using obsolete technologies, and that one of those costs is that you will not be supporting "Classic ASP".

Option 2: Write some C# code to produce COM wrappers to your services. The Classic ASP code (or VB6 or VBA or whatever) can call COM objects without having any idea they're using modern code developed with modern tools.