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://

**Do you want to request a feature or report a bug?

Feature?

What is the current behavior?
Session object ACLs require both the key and the api_id field of the ACL definition to match.

If they mismatch the API does not throw an error.

What is the expected behavior?

The Gateway API should report the discrepancy to stop the token from being generated.

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 ulimit setting should be checked when APISIX starts，if user limits too small(like 1024), APISIX should prompt to modify, otherwise, the performance is low

Environment

• apisix version (cmd: apisix version):
• OS:

virtual host options

1.目前针对 http服务，采用 ip + 端口，的探活机制
2. 业务接入网关把ip与端口上传到soul-admin

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

As seen in code coverage: https://codecov.io/gh/serverless-nextjs/serverless-next.js/tree/master/packages/serverless-components/domain, domain component has 0% coverage.

Adding tests for this should get us from 79% to ~90% overall coverage.

@SarKurd I remember you wanted to add tests for this. Let me know if you are still interested to add tests or someone else can also take it up

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.