Matt Connew

Closing this issue on the presumption that this solves the problem for you. If it doesn't, feel free to reopen.

It worked on an earlier version as CoreWCF wasn't enforcing authentication, that was needed to be done in application code (when configuring your middleware) before the call into CoreWCF. When...

> We're using a domain account for the app pool and SPN were setup long time ago when we were still using .NET Framework WCF service I think this might...

@dandesro71, I just noticed something in your earlier reply, that the client and server are on the same machine. Is the client using the hostname in the url or localhost?...

You're correct in that this can now go away. Unfortunately I made the mistake of making it public so it's technically part of the public API surface. This is going...

I don't think we have config support for WebHttpBinding yet as the two features were being developed at the same time.

If this is an important scenario to you, I can point you to the relevant place where the implementation needs to be added. It's mostly copying code from .NET Framework...

Can you provide 2 simple repro projects, one on .NET Framework which has the expected behavior, and another with CoreWCF which is failing?

@rashmidusane, if you check the output from starting the service, it should tell you the path that the WSDL is listening on. You can open that path in a browser...

Merged into feature/queue branch and will merge to main when ready to release.