0

There is my configuration: 

client app->WCF service (http://serverhost:8082 + SignalR service http://serverhost:8083)

I use bdtunnel from Sebastien Lebreton (https://github.com/sailro/Bdtunnel)

client app->bdtunnel:8080 (it forwards: localhost:8182->server:8082)->WCF service

It works fine.

The question is: is it possible to forward SignalR connection via the same tunnel on port 8080?

ZedZip
  • 4,355
  • 8
  • 43
  • 81
  • I don't know answer to your question and did not use Bdtunnel but what's the point of tunneling HTTP (long polling, serverSentEvents) over HTTP? I don't think Websocket transport can be tunneled like this at all... – Pawel Dec 15 '15 at 21:57
  • It may be useful when for example available 80, 443, 8080 ports only but behind of firewall some services work on other ports – ZedZip Dec 16 '15 at 08:49
  • In that case you should try the longPolling transport - I think it has the biggest chance to work. – Pawel Dec 16 '15 at 17:29
  • SignalR uses LongPolling too. But I already use SignalR in my service and the task is how client app can work with it via tunnel – ZedZip Dec 17 '15 at 08:47
  • What I am saying is that if SignalR can work at all with tunneling the SignalR longPolling transport will be the easiest to tunnel. In other words - instead of relying on the client to select the transport force the SignalR client to use the longPolling transport. – Pawel Dec 17 '15 at 17:08
  • ah, I see. How SignalR server can force to select longpolling transport? – ZedZip Dec 18 '15 at 13:09

0 Answers0