1. Environment

1a. Operating system and version

Manjaro 21.1.0 Pahvo (x86_64 Linux 5.4.135-1-MANJARO)

1b. Caddy version (run caddy version or paste commit SHA)

2.4.3

1c. Go version (if building Caddy from source; run go version)

1.16.6

2. Description

data race found

Caddy config:

{
	"admin": {
		"config":

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里面提各种问题，谢谢配合。

Task export inconsistent with actions

In JS mode, exporting tasks as module.exports = class SomeTask causes AH to throw an error when trying to execute it ' task not found' but exporting as exports.someTask = SomeTask works. Actions work either way.

From @evantahler:
actions have this line https://github.com/actionhero/actionhero/blob/v24.0.4/src/initializers/actions.ts#L65-L67
where

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 😄

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