SignalR typescript client: there is no way to catch authorization errors

[antonGritsenko]

Is there an existing issue for this?

• I have searched the existing issues

Describe the bug

I have very simple case: the hub is protected by the authorization policy, so some users can get 302 error when connecting to the hub. I need to catch this and show some some info of the client.

Expected Behavior

I can catch 302 errors.

Steps To Reproduce

connection: signalR.HubConnection;

    this.connection = new signalR.HubConnectionBuilder()
    .withAutomaticReconnect()
    .withUrl(environment.apis.default.url + `/signalr-hubs/call-tracker`, {
      accessTokenFactory: () => this.oAuthService.getAccessToken(),
    })
    .build();

this.connection
      .start()
      .then(() => {
        this.callTrackerConnected = true;
        this.callTrackerStatus = "OK";
        console.log('Connection started');
      })
      .catch(err => {
        this.callTrackerConnected = false;
        this.callTrackerStatus = "ERROR";
        this.callTrackerError = err;
        console.error("Enable to connect to SignalR", err)
        this.connection.stop();
      });

I'm always getting 'Conection started' message in the console and this.connection.state is always Connected

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

[BrennanConroy]

302 isn't an error, hence why the connection ends up with "Connection started".

It's also not a status code you can get any information about if you made fetch not follow redirects:
https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch#checking_the_response_type

opaque redirect responses have a status of 0, an empty header list, and a null body

[dotnet-policy-service]

This issue has been resolved and has not had any activity for 1 day. It will be closed for housekeeping purposes.

See our Issue Management Policies for more information.