https

Three or four parameters of header_down use Regex, and one does simply overwriting.
Caddy did not simply make a case-sensitive distinction of the header key value when it overwrites it, but I experienced a case-sensitive distinction of the header key value when I used Regex.
I think it is not intended.

Reproduction of issue.

example.com {
        reverse_proxy {
                t

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

Feature request

Feature description

The generated and installed config files permission are too open, any user logined on the system can read and write them. So i suggest append a chmod command into Extract tar step to keep config files more safty.

How the feature is useful

如：xxx app + www.xxx.com

不要在此issue里面提各种问题，谢谢配合。

Currently we have a mix of:

• Out of memory error.
• Out of memory error
• out of memory error
• out of memory
• out of memory.
• out of memory [some context]

All these should be adjusted to use the same wording for consistency and it should also make the executable a little bit smaller 😄

We had an issue where an api user was using the incorrect parameters on an API call. Having this feature would have made the API fail instead of proceeding. The bug would been found earlier.

I can see where this would be a hassle on many cases, But it would be nice for new projects.

I suppose it could be a global config item that could be overridden at the individual action level:

For

It should allow rewriting http Host header like ngrok does with param -host-header=example.com