ThreeMammals / Ocelot

.NET API Gateway

Home Page:https://www.nuget.org/packages/Ocelot

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

SignalR no connection in `ws` mode

mtlive opened this issue · comments

I tried everything in documentation for using signalR in websocket mode but couldn't get it to work.
In our staging servers I get the "Handshake was canceled error" and in debug it takes so long that it switches out from ws.

Expected Behavior

Actual Behavior

image

Specifications

  • Version: 23.3.0
  • Platform: .NET 8 (Windows)
  • Subsystem:

Also added services.AddSignalR();
Confiuration:

"Routes": [
   {
     "DownstreamHostAndPorts": [
       {
         "Host": "192.168.10.209",
         "Port": 5003
       }
     ],
     "DownstreamPathTemplate": "/{everything}",
     "DownstreamScheme": "ws",
     "UpstreamPathTemplate": "/chat/{everything}",
   },
],
"DynamicRoutes": [],
"Aggregates": [],
"GlobalConfiguration": {
  "RequestIdKey": null,
  "ServiceDiscoveryProvider": {
    "Scheme": null,
    "Host": null,
    "Port": 0,
    "Type": null,
    "Token": null,
    "ConfigurationKey": null,
    "PollingInterval": 0,
    "Namespace": null
  },
  }
}

I believe this isn't an Ocelot issue, so I'll turn it into a discussion...
Other developers have been utilizing Ocelot's SignalR feature for years.