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

comments: apache/apisix#2121 (comment)

t/plugin/limit-req.t ..................... ok

#   Failed test 'TEST 1: log rotate - response_body_like - response is expected (2020-08-31_10-25-32__access.log 2020-08-31_10-25-31__access.log 2020-08-31_10-25-33__access.log . 2020-08-31_10-25-32__error.log error.log 2020-08-31_10-25-33__error.log access.log 202

virtual host options

在soul-admin后台，每个插件的handler处理，为一个json字段。每个插件都不相同，现在需要在插件管理，新增一个模块配置，来配置handler字段的内容，描述。 前端根据这个配置，来动态的渲染配置

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

Describe the bug
JSON data files for SSG pages (e.g. `_next/data/{build id}/file.json) are not being cached by Cloudfront, meaning that subsequent calls always go to the origin (and trigger the Lambdas@Edge).

To Reproduce

1. Deploy a website with at least one SSG page.
2. Visit the SSG page once. This should cache the JSON data.
3. Refresh that page and observe the x-cache respons

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.