Question

I have created my own IConnectionIdGenerator implementation which for simpicty in my webforms application names the client connection Id by the EmailAddress.ToLower() of the logged in authenticated user (if that’s not available then it defaults back a guid).
Calling the client from my page code behind all works fine.

hubContext.Clients[LoggedInUser.EmailAddress.ToLower()].updateProgress(i)

However it seems that if I open another browser or tab with the same logged in user both the foreverframe connection on both windows keeps giving a 301 result then a 200 result alternating and repeating.

I assumed that assigning the same connection Id would just give me an easy way to make sure messages correctly go to the correct user of the system no matter where they connected.

Do they always have to be unique and will I have to build another layer to manage connections to logged-in user accounts or am I missing a trick here?

Answer 1

Connection ids have to be unique. If you don’t make them unique then one will kick the other connection offline. Internally we use the connection id as a unique identifier for a connection and we disconnect dupes.

If you get repeated 301 responses it’s likely because you have a folder in your app called signalr, and it isn’t directly related to sharing connection ids.