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

The default_conn_delay of the limit-conn plug-in is used to control the delay of forwarding to upstreams when the connection exceeds a certain threshold, but after actual testing, it is found that this delay time is not strictly in accordance with the configured delay time.

https://github.com/openresty/lua-resty-limit-traffic/blob/master/lib/resty/limit/conn.lua#L98-L101

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