Skip to content

Commit ae66be1

Browse files
authored
Update how-to-develop-emulator.md
If the "LimitToEndpoint = true" configuration is not added to the CosmosClientOptions and the user is testing locally, the cosmos client never returns a response and just continually spins. It appears that it just keeps trying to connect, but doesn't timeout correctly or has no limit. This seems to fix that issue.
1 parent f3a807d commit ae66be1

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/cosmos-db/how-to-develop-emulator.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -476,7 +476,8 @@ Use the [Azure Cosmos DB API for NoSQL .NET SDK](nosql/quickstart-dotnet.md) to
476476
> {
477477
> ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator
478478
> }),
479-
> ConnectionMode = ConnectionMode.Gateway
479+
> ConnectionMode = ConnectionMode.Gateway,
480+
> LimitToEndpoint = true
480481
> };
481482
>
482483
> using CosmosClient client = new(

0 commit comments

Comments
 (0)