How to use in Microsoft Azure with load balancing about aspnetcoreratelimit HOT 4 CLOSED

Add NuGet for:

Microsoft.Extensions.Caching.Redis

In your Web App startup, add

   services.AddDistributedRedisCache(options =>
   {
       options.Configuration = "your redis connection string"; // e.g. contoso5.redis.cache.windows.net,abortConnect=false,ssl=true,password=...
       options.InstanceName = "master";
   });'

This will ensure that the Redis implementation of IDistributedCache is registered into your DI container.

Then register AspNetCoreRateLimit as per the wiki:

   // Bind Settings and Policy
   services.Configure<IpRateLimitOptions>(Configuration.GetSection("IpRateLimiting"));
   services.Configure<IpRateLimitPolicies>(Configuration.GetSection("IpRateLimitPolicies"));

   // inject counter and rules stores
   services.AddSingleton<IIpPolicyStore, DistributedCacheIpPolicyStore>();
   services.AddSingleton<IRateLimitCounterStore, DistributedCacheRateLimitCounterStore>();

Don't forget to call app.UseIpRateLimiting() in your Web App startup too.

And don't forget to add all the config into your appSettings.json

from aspnetcoreratelimit.

@oatsoda
hi
i do this but show me this error:
RedisConnectionException: No connection is available to service this operation: EVAL; SocketFailure on localhost:6379/Subscription

from aspnetcoreratelimit.

@MajidDehnamaki Perhaps your Redis connection string is wrong? Or some sort of Firewall/Connectivity issue between your App Service (I assume you are using a standard Azure App Service?) and your Redis.

It doesn't sound like an AspNetCoreRateLimit issue...

You might want to test out using the IDistributedCache interface directly and once you get that working, then turn on the rate limiting.

from aspnetcoreratelimit.

Also, if you are using AspNetCoreRateLimit.Redis package with services.UseRedisRateLimiting() then you don't need to add the policy stores as they are added internally for you.

from aspnetcoreratelimit.