Web

Description

The issue is described here

You cannot possibly be held responsible for all contingencies for every system, that would be unreasonable. However, it would benefit the community, especially those of newcomers, were this issue at least mentioned as known in your docs. A timestamped solution would be

First check

• I added a very descriptive title to this issue.
• I used the GitHub search to find a similar issue and didn't find it.
• I searched the FastAPI documentation, with the integrated search.
• I already searched in Google "How to X in FastAPI" and didn't find any information.
• I already read and followed all the tutorial in the docs and didn't find an answ

Context:

System:

• OS: Windows 10 10.0.18363
• Memory: 2.46 GB / 15.78 GB

Binaries:

• Node: 16.9.1 - C:\Program Files\nodejs\node.EXE
• npm: 7.24.1 - C:\Program Files\nodejs\npm.CMD

Languages:

• Bash: 5.0.17 - C:\WINDOWS\system32\bash.EXE

npmPackages:

• playwright: ^1.18.0 => 1.18.0

Provide the steps to reproduce

1. Run LH on https://output.jsbin.com/vulerujohi for just

Checklist

• Dependencies installed
• No typos
• Searched existing issues and docs

Issue Description

When using the RateLimiter Middleware with a rate between 0 and 1 all events will be rejected instead of applying the specified rate. E.g.: e.Use(middleware.RateLimiter(middleware.NewRateLimiterMemoryStore(0.5)))

I am not saying that it is a common use case to have

The project is on 2021 (#2338). Docs should be updated

Questionaire

• I'd like to write this documentation
• I'd like to write this documentation but I'm not sure what's needed
• I don't have time to add this right now, but maybe later

🚀 Feature

(A clear and concise description of what the feature is.)

Have you spent some time to check if this issue has been raised before?

(Have you googled for a similar issue or checked our older issues for a similar bug)
Yes

Have you read the Code of Conduct?

Yes

Pitch

A common way to mana