Next line returns 200 as status https://github.com/Kong/kong/blob/c817fada7a514d84f6e0aab7461605c71bf3a841/kong/plugins/cors/handler.lua#L13

Internet says it should return 204:

• https://developer.mozilla.org/en-US/docs/Glossary/Preflight_request
• https://docs.microsoft.com/en-us/aspnet/core/security/cors?view=aspnetcore-3.1#preflight-requests

Internet changed its mind since 2018 https://

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

Issue description

The output data of the plugin_proxy_rewrite_args method in the apisix/t/lib/server.lua file is disordered, which will result in unstable test cases using this method. E.g:

--- request
GET /plugin_proxy_rewrite_args?name=james&age=36
--- response_body
uri: /plugin_proxy_rewrite_args
age2: 36
name2: james
--- no_error_log
[error]

--- r

Feature Request

1.Add a resource management menu, mainly add, delete, edit and query the buttons and menus of all pages
2.Remove menu User, Role, Resource to User Management
3.Remove menu Plugin, PluginHandler,Authentication,Metadata,Dictionary to Basic Configuration
4. When adding a new plugin, add the corresponding button to resource
5. Put the newly added resource menu to permission con

virtual host options

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.

Currently both lambdas can only have the same arn role (if set). However it would be better to follow the same approach that there is for the name field

  roleArn:
      defaultLambda: arn
      apiLambda: arn

The reason I say this is because I wouldn't want to give the defaultLambda access to the database.

sls invoke is useful for testing our API one request at a time.

It would be nice to spin up a local version of the API on localhost to enable us to develop our frontend apps against it, and to more easily run integration and E2E tests.