expected result:
example.com?param=abc -> will become example.com
example.com/?param=abc -> will stay example.com/

actual result:
example.com?param=abc -> become example.com
example.com/?param=abc -> stays example.com/?param=abc

Description

For example,
https://github.com/apache/apisix/blob/a1482dd78cf8494e1ce9f6ca246d9afde3aa733a/apisix/plugins/authz-keycloak.lua#L664-L666
will tell the client about the token endpoint configuration.

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

Version

1.8.x

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

validationServerGrpcMaxSizeBytes is too low, so when deploying gloo in an env with more than 1000 vs/us for example the gateway will break and nothing will be served to envoy.

increasing validationServerGrpcMaxSizeBytes to 100mb by default has no impacts on the product and will avoid breaking the control p

Follow up on #1245

Add a check to validate that x-extensible-enum properties have a string type.

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.

Describe your problem(s)

In the "Complexity Analysis" tab in GraphQL try-out page in devportal, we can see only the complexity Values of each field. If we want to know the complexity value or the depth value, we have to calculate ourself manually. Instead, it would be a nice to have feature to have the possibility to display the calculated complexity/depth values on a button click. So before

Issue description

Catch all issue to improve i18n:

• Replace Route List with Routes
• Use a shorter label for Title and Description

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

describe issue

• config impl
• registry impl
• common
• adaptor opensource
• gov impl

Lack of unit tests

how to solve

Refer to the example （governance-impl /test）