api-gateway

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

2.5.1.0

Current Behavior

When calling kong.response.exit(), the function automatically sets the Content-Length header on the response even if the Transfer-Encoding header is present. This is in violation of RFC 7230 3.3.2:

A sender MUST NOT send a Content-

Improved or typo fixed.

add new diagram before https://github.com/apache/apisix/blob/master/docs/en/latest/architecture-design/apisix.md#plugin-loading-process

Solution

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

Expected Behavior / New Feature

Support sticky sessions for ServiceDiscoveryProviders

Actual Behavior / Motivation for New Feature

When using websockets with ocelot in a distributed system, problem can arise since ocelot, as far as i know, doesn't support sticky sessions when working with service discovery providers.

The functionality could be great if it could work with both consul

Task

Currently, We use the AES algorithm to encrypt the password and provide the password back to the front end. I think It's not safe.

I suggest the following optimization:

1. The API does not return the password field. See `org.apache.shenyu.admin.controller.DashboardUse

Hi,

I've started using spring cloud gateway as front door for set of microservices, and using oauth2. When implementing bean "ReactiveOAuth2AuthorizedClientManager" to customize some prosperities, a duplicate bean definition exception is throw at runtime:
_org.springframework.beans.factory.NoUniqueBeanDefinitionException: No qualifying bean of type 'org.springframework.security.oauth2.client.R

Describe the bug
In glooee, the 18-settings.yaml file is generated incorrectly if extauthCustomYaml is provided

To Reproduce
Steps to reproduce the behavior:

cat <<EOF > values.yaml
global:
  extauthCustomYaml: true
  extensions:
    extAuth:
      extauthzServerRef:
        name: external-auth-server
        namespace: kube-gloo-system
      httpService:
        pat

Issue Summary

Building with serverless results in an error:

Build error occurred
TypeError: Class extends value undefined is not a

If not for some particular exceptions, the status code returned from our WebAPI on error is always 500, regardless of the kind of error.

If an object already exists, for example, it should be returned as 409. If the object does not pass the schema validation, it should be a 415.

Go through the whole WebAPI and verify that the status codes are being returned correctly.

Hint: Error cl

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

The hydrator have only Basic auth - see config: https://www.ory.sh/oathkeeper/docs/pipeline/mutator/#configuration-4, however for more flexibility, similiar pre-authorization mechanism could ba added as in the instropsection authenticator handler: https://www.ory.sh/oathkeeper/docs/pipeline/mutator/#configuration-4

**Descri

Right now settings are just passed in through the settings file. This is somewhat limiting if there is a value that will be dynamic with deployments (such as a docker image file, etc.) We should support accepting settings through environment variables, the CLI, the current settings file, and any mix of those.

The order of precedence with mixed should be CLI -> environment -> config file.

If