Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Custom Negotiation Response Key Handling #49

Closed
AlirezaSN opened this issue Apr 14, 2019 · 2 comments
Closed

Custom Negotiation Response Key Handling #49

AlirezaSN opened this issue Apr 14, 2019 · 2 comments

Comments

@AlirezaSN
Copy link

Hi there , What can we do when server negotiation response keys are different from hard-coded keys in framework ? for example "ConnectionId" instead of connectionId.🧐
Thanks.
@moozzyk
Copy link
Owner

moozzyk commented Apr 14, 2019

SignalR will have the same casing for keys specific to SignalR protocol. As per the spec connectionId is using camel case. If the server responds with different casing it is a violation of the protocol and this client will not work with a server like this. Can you show an actual case where you see the mismatch?

@moozzyk
Copy link
Owner

moozzyk commented Apr 22, 2019

Closing for now because this does not seem to be an issue with the client.

@moozzyk moozzyk closed this as completed Apr 22, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@moozzyk @AlirezaSN