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

https://docs.solo.io/gloo-edge/master/guides/security/rate_limiting/simple/

          anonymous_limits:
            requests_per_unit: 

should be:

        anonymousLimits:
          requestsPerUnit: 10

See https://docs.solo.io/gloo-edge/master/reference/api/github.com/solo-io/gloo/projects/gloo/api/v1/enterprise/options/ratelimit/ratelimit.proto.sk/

See https://github.com/apiman/apiman/blob/master/.github/workflows/verify.yaml

Might as well also add builds for Java 11 and 15 while at it.

Upgrade Gradle version in github-integration module.
Drop jcenter support.

Issue description

When a page is not clicked for a long time and session expired, browser will be redirected to the login page by XHR : http://139.217.190.60/user/login?redirect=%2Fuser%2Flogin
the redirect param is not the last page user viewed URL and cannot redirect to the old page.

Environment

APISIX 2.6 with API

We tried to build dashboard docker image for ARM in #197 but failed. Since I could build dashboard docker image on m1 so there's nothing to do with the building process itself.

And since it stuck at yarn build, a large chance is free Github Actions machine is lack of memory since we also deploy QEMU to simulate arm environment, as [ref](https://stackoverflow.com/questions/59868448/rpc-error