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

I hope that apisix could be configurated the listening address.
In some special cases, for example, I plan to use a combination of APISIX and Keepalived to achieve high availability.
I will turn on the relevant Linux kernel parameters (to enable the program to listen the IP that does not exist on the local host):

echo "net.ipv4.ip_nonlocal_bind=1" >> /etc/sysc

Describe the bug
The glooctl get upstreams function list for AWS Lambdas does not distinguish between multiple versions of the same Lambda function.

To Reproduce

1. Apply an AWS Lambda Upstream that contains multiple versions of the same function.
2. Run glooctl get upstreams
3. Note a display like the following. For example, there are 4 versions of the contact-form Lambda a

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.

These errors appear during the build process. For example

zally-ruleset-zalando/src/test/kotlin/org/zalando/zally/ruleset/zalando/DateTimePropertiesSuffixRuleTest.kt: (17, 9): Name contains characters which can cause problems on Windows: "
zally-ruleset-zalando/src/test/kotlin/org/zalando/zally/ruleset/zalando/DateTimePropertiesSuffixRuleTest.kt: (46, 9): Name contains characters which can 

Issue description

in http://139.217.190.60/routes/list site:

Expected behavior

How to Reproduce

1. Go to '...'
2. Click on '...

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