WCF ServiceRoute and Tcp

Question

I have a WCF application hosted in IIS in which I use WsHttpBinding, with aspnetCompatibility, since I want to use the RouteTable function to route many calls to a single service.

everything worked as expected, no problem here.

Then I added the tcp endpoint to the service (using its source url) and called this service the client, everything worked here without problems.

Then I changed the client URL with a routable URL and called the method using the tcp endpoint, I got a socket error, which I expected.

But then I launched the wsHttp client with the routed URL (which worked) and launched the tcp client with the routed URL (which surprisingly worked)

Are tcp and http requests being sent through the same pipeline?

Answer 1

To my knowledge, the System.Web.Routing script is only supported for HTTP-based endpoints, since netTcpBinding does not really use URLs in the same way.

- larsw

Answer 2

According to the Microsoft Documentation on ServiceRoute , it is only intended to support base addresses without extension through HTTP transport .