Releases: Azure/azure-signalr
Releases · Azure/azure-signalr
Release v1.19.0
Features:
- Support SignalR
client result
(.NET7.0
+). - Support CloseOnAuthenticationExpiration. Set this option to enable authentication expiration tracking which will close connections when a token expires.
Bug Fixes
- Fix #1652: Configuration issue and a few improvements #1654.
- Fix #1679:
HubConnectionContext.UserIdentifier
is null if negotiation with Management SDK and set user ID #1691. - Fix #1700: proxy not applied to serverless transient mode #1708.
Improvements
- Reduce retry interval when AAD auth failed #1451.
Release v1.18.3
Features:
- Add 2 properties
InitialHubServerConnectionCount
andMaxHubServerConnectionCount
and obsoleteConnectionCount
Bug Fixes
Release v1.18.1
Release 1.18.0
Feature
- Add
AuthType=azure
,AuthType=azure.msi
,AuthType=azure.app
supports for connection string.
Release 1.17.1
Bug Fixes
- Fix the Azure Function binding issue #1603
Release 1.17.0
Bug Fixes
- Fix the regression issue that for the single endpoint scenario, send message failure does not throw (#1582)
- Improve the error handling when a message fails to send with multiple endpoints (#1582)
- "DefaultMessageRouter" filters out "offline" endpoints so that messages will not send out to offline endpoints
- You can customize your own message router if you'd like to make sure exceptions throw when some endpoints are offline.
- Fix the endpoint hot-reload logic to support "ClientEndpoint" and "ServerEndpoint" property (#1592)
Release v1.16.1
Features
- Add server endpoint and client endpoint as optional parameters of a
ServiceEndpoint
constructor so that users can customize them with AAD auth. #1586
public ServiceEndpoint(Uri endpoint, TokenCredential credential, EndpointType endpointType = EndpointType.Primary, string name = "", Uri serverEndpoint = null, Uri clientEndpoint = null)
Fixes
- Fixes the ackable message time out problem when multiple SignalR endpoints exist. #1576
Release v1.16.0
Features
- Support the customization of endpoints for servers to connect to ASRS in code or config. #1564
Users have two ways to setserverEndpoint
orclientEndpoint
.- Option 1: in connection string:
serverEndpoint=...
- Option 2: in the ctor of
ServiceEndpoint
:new ServiceEndpoint(new Uri(endpoint), new DefaultAzureCredential()) { ClientEndpoint = clientEndpoint, ServerEndpoint = serverEndpoint }
- Option 1: in connection string:
- Allow customization of endpoints for clients to connect to ASRS in code.#1564 See the code sample above.
- Expose connection capacity in metrics of ServiceEndpoint #1567
- Change the default endpoint router from random to weighted random #1568
Fixes
- Fix the message order problem with multiple service connections. #1571
Release v1.15.2
Fixes
- Fix the bug that Management SDK connection count is fixed to 3
RestClient
SetStatusCode
onHttpRequestException
on .NET 5 or above runtime.