asp.net - SignalR 2 & Javascript Client to Server A to Server B -

i have following architecture setup.

client (javascript) => server (has signalr server) , client (javascript) => server b (also has signalr server)

i want know if can make so.. client => server => server b

where client can connect signalr on servera, , using rewrite rules, allow connections uri /backend/signalr go through server b ?

the reason behind architecture because have front-end serves site amongst other things, back-end processing application requires feedback client (server b client a). use signalr on both servers, , client can connect directly both.

the reason question remove back-end server being public facing , allow internal network requests, that's fine , doable, problem have manage client's feedback updates server b client a, have typically route through server a.

i saw answer here @ signalr iis 10 , arr 3.0 , had similar issue, except didn't have first proxy server serving signalr aswell.

i guess additional different case has 2 signalr implementations in architecture.

another thought perhaps done using web.config , ip restrictions on server b allowing direct communication server a, , uri's signalr allow public facing - prefer remove entirely if possible.

our application uses asp.net 4.6 iis 10

i solved , removed backend server receiving requests client browser directly.

i created 'proxy' sat in server hub definition class when requirement backend server required, create c# client connects internal servers. created needed methods backend server emit / send via signalr frontend server, , pushed client javascript browser.

i think application routing requests feature in iis, since doesn't support https, implementation gets job done.

if there other implementation or thoughts this, i'd love know others think. did job done me in end , can remove backend server being public facing due signalr requirement had.