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

See apache/apisix#3308 (comment)
@jenskeiner

Could it be possible to have a warning message when installing a rock that contains a module that is already provided by another rock? Or is there already an option for this and I didn't find it?

At least with Luarocks version 3.2.1 I verified that there are no warnings for this case.

However it seems that Luarocks is aware of the collision and installs the new module under another name and

The ported markdown documentation attempts to glean technical documentation that is relevant to moonjit such as installation and execution instructions, API, etc. It does not have benchmark numbers, sponsorship acknowledgements or contact details since they are not relevant to moonjit.

In the process however, a number of cross-links have gone missing and the port also may have errors, formatti

Language request for Dart.