reverse-proxy

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":

Can anyone please help me out. I'm getting error while generating KONG client credentials on HTTP port 8000.

{ "error_description": "You must use HTTPS", "error": "access_denied" }

I have added trusted_ips = 0.0.0.0/0,::/0 in kong.conf also, but it didn't work.

On contexts with many APIs and APIs calling other APIs in chains, having too many spans in the zipkin/jaeger dashboards may lead to a too complex usage of such dashboards and of not necessary big data volumes.

For Tyk's admin team, the steps representing the time spent in each Tyk middleware are much valuable.

But the upstream APIs teams just want to know the global time spent in Tyk interna

Issue description

在Consumer中添加 consumer-restriction 插件，里面的 type 能否支持下route_id，这样我们就能基于 consumer 的纬度来限制能访问到的 route，现在的版本我看了下只支持 consumer_name 和 service_id，即只能在 route 纬度来限制 consumer 或者 只能在 consumer 纬度来限制能访问的 service。

需求场景：同一组service下可以有多个route，但是可能有部分route是不用鉴权的或者需要额外申请才给开通，如果能在consumer纬度支持一下 route_id，那样就能更精细化的赋权，且不用每个用户来申请权限都需要对route接口发起一个PATCH请求。

插件文档：https://apisix.apache.org/docs/apis

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered

Is your feature request related to a problem? Please describe.

As observed during #261, users can accidentally set timeouts inconsistently. A concrete example is that one can set a User facing timeout lower than any backend timeout, such that requests may fail early.

Describe the solution you'd like

We should provide some sanity checking to prevent unintended timeout behavior.

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 😄