After setting up a new BizTalk server I kept getting HTTP status 404 with substatus 0 when testing a service through the front end web, but when surfing directly to the BizTalk WCF service I received the WSDL.
In the IIS logs I could see that my direct surfing resulted in a GET.
Using PostMan I got the same behaviour of WSDL from a GET and 404 from a POST.
The problem was that I had imported the bindings for our HTTP environment instead of our HTTPS bindings.
Enabling transport security in the bindings,
Enabling transport security in the bindings,
and selecting certificate as the client credential type fixed the issue.
