search

pusher / pusher-websocket-dotnet

Pusher Channels Client Library for .NET
MIT License
112 stars 113 forks source link

403 Forbidden should be handled when authenticating user #89

Closed heath3n closed 3 years ago

heath3n commented 4 years ago

According to the docs, the server should handle a rejected authentication by sending a 403 Forbidden status. In practice, this causes an NRE. We are working around this by ensuring we send back a body with the key auth like { auth: 'invalid'} but it would be great if the library could just recognize an error occurred from the status code.

elverkilde commented 3 years ago

This issue was fixed in #104 which was released as version 2.0.0. Please be aware that this is a major release, with several breaking changes. We have written a migration guide here:

https://github.com/pusher/pusher-websocket-dotnet#migrating-from-version-1-to-version-2