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

1. the pluginx wolf-rbac 's login url /apisix/plugin/wolf-rbac/login return the json but header give the content-type is text/plain, when the browsr crossdomain post then show the cors error, please change the plugin login post give the Content-type to application/json

2. The wolf-rabc 's login uri /apisix/plugin/wolf-rbac/login will lose the cors plugin add the

Is your feature request related to a problem? Please describe.
Currently, there's no way in Gloo Edge to perform similar than what the regex_rewrite option provide.

Describe the solution you'd like
Expose the regex_rewrite (https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/route/v3/route_components.proto#envoy-v3-api-msg-config-route-v3-redirectaction) option in Gloo Edge

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.

Docker Compose configurations still refer to PostgreSQL 9.6 Docker image:
https://github.com/zalando/zally/blob/master/docker-compose.yaml
https://github.com/zalando/zally/blob/master/docker-compose-bark.yaml

According to the official release timeline the 9.6.x branch will have the final release (i.e., no more security updates after) pretty soon:
https://www.postgresql.org/support/versioning

Feature request

Background

At present, some plugins in Apache APISIX have metadata configuration items. The current dashboard project cannot support setting these contents. We need to support it. This requires adding APIs at the backend and pages at the frontend.

About metadata

Metadata is a mechanism provided by Apache APISIX to store some global configuration content for plugins

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