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

Improve Docs

Please describe which part of docs should be improved or typo fixed

Currently in getting-started, there would always be a $ at the front of each command, which makes users hard to do three-click to directly copy the whole command and run without modification. They have to manually delete `

virtual host options

https://github.com/actions/cache/blob/master/examples.md#node---yarn

See also... https://dev.to/mpocock1/how-to-cache-nodemodules-in-github-actions-with-yarn-24eh (Read the comments also)

Would there be any appetite to add a rule that checks for the inclusion of required and optional fields in your API?

Hi @juzhiyuan do we need to delete this action, or use submodule to make it running

Originally posted by @Yiyiyimu in apache/apisix-dashboard#1059 (comment)

Currently we need maintainers to upload release images to Dockerhub manually. Following https://docs.github.com/en/actions/guides/publishing-docker-images, we could find how to use GitHub actions to do the upload step, for example, triggered by release branch.

However, due to Apache rules, there are chances that we are not allowed to use Github Actions provided by docker. So we might need to us