Closed gtwilliams03 closed 7 years ago
Actually, I am going to close this, since I think I have the same issue as #1. If I put this url (without the redundant url at the beginning, i.e., change:
https://api.mydomain.comhttps//api.mydomain.com/signalr/connect?transport=longPolling&clientProtocol=1.5&connectionToken=[TOKEN]&connectionData=%5B%7B%22name%22%3A%22myhub%22%7D%5D
to
https//api.mydomain.com/signalr/connect?transport=longPolling&clientProtocol=1.5&connectionToken=[TOKEN]&connectionData=%5B%7B%22name%22%3A%22myhub%22%7D%5D
and POST that to my server, it replies with some happy SignalR stuff:
{
"C": "d-A0E73A60-B,1|C,0|D,2",
"S": 1,
"M": []
}
So now I need to figure out how to put this fix in as well.
In case it helps, I also had the issue #1 and had to edit line 1274 of the signalR.js file in node-modules/signar-no-jquery from this:
url = baseUrl + connection.url,
to this:
url = baseUrl + connection.appRelativeUrl,
@gtwilliams03 Sorry if this is a dumb question, I just can't figure out if I need to import it, and where.
did you end up getting the hubs to work? my call to createHubProxy
does not contain my server methods
Using this in a React-Redux app and I can see my API responding to calls - but I cannot get the hubs responding. In other SignalR projects I have done, you have to include /signalr/hubs from the source to list out the available hubs. Do you know where you do this in this project? Sorry if this is a dumb question, I just can't figure out if I need to import it, and where.
I am also getting the strange long polling double url in the
Opening long polling request
logging line below.