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

As a User, I want to use oAuth2 with PKCE support, so that I can configure an oAuth2 connection without using client/secret.

I am using an IDP. which has implemented the Authorization Code Flow.

From the docs of the IdP:
The IdP implements the [Authorization Code Flow](https://openid.net/specs/openid-con

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.11.x (latest stable)

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

According to the envoy docs, certain HTTP/2 settings should be configured, based on the envoy deployment mode, trustworthiness of upstreams and downstreams and required support for protocol upgrades and downgrades. These settings include:

1. [Upstream HTTP/2 Protocol Options](https://www.env

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.

Follow up on #1245

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

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

Feature request

Please describe your feature

The current requirement to enable an authentication class plugin when creating a Consumer in Dashboard is inconsistent with the Admin API behavior. https://apisix.apache.org/docs/apisix/admin-api#consumer
Inconsistent behavior can lead to a number of problems #2436

Describe the solution you'd like

Users can create a Consumer in Das

Alpine Linux is affected by a serious security CVE-2022-28391 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-28391

The AlpineLinux Release Note https://alpinelinux.org/posts/Alpine-3.12.12-3.13.10-3.14.6-3.15.4-released.html

We should update the currently used Alpine Linux image version.

Describe the issue

The connection from sdk to server is plug-in,
see #com.tencent.tsf.femas.governance.config.impl.ServerConnectorConfigImpl,

The current practice is http connection polling the data form femas server, We want to support grpc protocol to improve performance