Using the version 2.1.0, I'm getting an empty response

[andrecarlucci]

I get the 429, but also an empty response :(
I'm using AspNetCoreRateLimit 2.1.0 with netcoreapp2.2

appsettings.json

"ClientRateLimiting": {
    "EnableEndpointRateLimiting": false,
    "StackBlockedRequests": false,
    "ClientIdHeader": "Pim-Auth",
    "HttpStatusCode": 429,
    "EndpointWhitelist": [
      "get:/index.html",
      "get:/swagger-ui.css",
      "get:/swagger-ui-bundle.js",
      "get:/swagger-ui-standalone-preset.js"
    ],
    "ClientWhitelist": [  ],
    "GeneralRules": [
      {
        "Endpoint": "*",
        "Period": "15m",
        "Limit": 2
      }
    ]
  }

ConfigureServices

            services.AddOptions();
            services.AddMemoryCache();
            services.Configure<ClientRateLimitOptions>(configuration.GetSection("ClientRateLimiting"));

            services.AddSingleton<IClientPolicyStore, MemoryCacheClientPolicyStore>();
            services.AddSingleton<IRateLimitCounterStore, MemoryCacheRateLimitCounterStore>();

Configure (first line)

app.UseClientRateLimiting();

Any thoughts?

[sharyex]

Try setting the QuotaExceededMessage option in the json config.
This is where the message is handled if you want to fiddle with it: ReturnQuotaExceededResponse

Working fine for me in .NET Core 2.1, tho I had to modify the project and compile it myself to resolve some dependency warnings instead of using the nuget package, maybe something breaks for 2.2, try self compiling it as well.

[andrecarlucci]

@sharyex, setting QuotaExceededMessage did the trick, thanks!