Fixing WCF HTTPS Endpoint 404 Errors

Windows Communication Foundation (WCF) may be considered an old technology, but many legacy .NET projects still rely on it. If you are working with WCF services hosted in IIS, you may encounter an issue when exposing services over HTTPS.

When the service is exposed over HTTPS, the <service name> defined in your web.config must exactly match the fully qualified type name of the service implementation class defined in the .svc file. If they do not match, WCF cannot resolve the endpoint, resulting in a 404 error.

Example of Incorrect Configuration

<service name="ServiceA">
    ...
</service>
    

Correct Configuration

<service name="ProjectA.Setup.Service.ServiceA">
    ...
</service>
    

This small detail often gets overlooked, but ensuring the names match is essential for WCF to properly locate and expose the endpoint when running over HTTPS. 

--NSA