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

When checking a request's remoteAddress, it's usually the address from which NIO received the request. While that's technically correct, Vapor servers are often hosted behind a reverse-proxy such as nginx. Therefore the original peer's address is often lost. To resolve this, it's not uncommon to set the original peer's address in a header such as X-Forwarded-For.

**Describe the solution you

Feature request

Place the access_log and error_log directives inside the main server block instead of http block.

Feature description

Disable access_log at http block:
File: /etc/nginx/nginx.conf

# ...
http {
    # ...
    access_log off;
    # ...
}
# ...

Enable per site access_log and error_log at main server block:
File: /etc/nginx/

Let's support at least reading "b3" header from a single string, most commonly traceid-spanid-1
It would also be nice to support optionally writing this, especially in message providers or others with constrained environments.

Expected behavior

As discussed on openzipkin/b3-propagation#21 and first implemented here: https://github.com/openzipkin/brave/blob/master/brave/src/main/java/bra

AnnotatedServiceBindingBuilder and VirtualHostAnnotatedServiceBindingBuilder currently don't share a common interface for its methods, such as pathPrefix() and exceptionHandlers(). This means, a contributor can add a builder method to one builder but not to the other by mistake. By making both builder extend a new interface AnnotatedServiceConfigSetters, we could prevent such a mistake.

Introduce

It has been more than three years since SOFARPC was open-sourced on April 10, 2018. RPC-related documents are mainly updated in June 2019. At that time, the document was relatively classic, and the core functions of RPC were introduced relatively clearly. However, with the iterative update of functions and the update of relate

Your Feature Request

Some applications are not case-sensitive on the URL parameters, and may look for arguments presented under any fantasist format. One could argue that we could turn the complete string to lower case before performing the lookup, but that would also change the values, which is not desired. A better approach would be to improve url_param, urlp, and urlp_val() to take a