Skip to content

Commit ef5845f

Browse files
authored
update link
1 parent 563f969 commit ef5845f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-signalr/signalr-howto-reverse-proxy-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ There are several general practices to follow when using a reverse proxy in fron
5252

5353
If you have configured multiple SignalR services behind your reverse proxy, make sure `negotiate` request and `connect` request with the same `asrs_request_id` query parameter(meaning they are for the same connection) are routed to the same SignalR service instance.
5454

55-
* For `ServerSentEvent`(SSE), make sure your reverse proxy doesn't buffer or cache response. For example, API Management lists the checkitems [here](/azure/api-management/how-to-server-sent-events.md) when configuring API for server-sent events.
55+
* For `ServerSentEvent`(SSE), make sure your reverse proxy doesn't buffer or cache response. For example, API Management lists the checkitems [here](/api-management/how-to-server-sent-events.md) when configuring API for server-sent events.
5656
*
5757
* When reverse proxy is used, you can further secure your SignalR service by [disabling public network access](./howto-network-access-control.md) and using [private endpoints](howto-private-endpoints.md) to allow only private access from your reverse proxy to your SignalR service through VNet.
5858

0 commit comments

Comments
 (0)