luajit

Is there an existing issue for this?

• I have searched the existing issues

Kong version ($ kong version)

2.5.1.0

Current Behavior

When calling kong.response.exit(), the function automatically sets the Content-Length header on the response even if the Transfer-Encoding header is present. This is in violation of RFC 7230 3.3.2:

A sender MUST NOT send a Content-

Issue description

feat: As a User, I want to have the port in the Host header when pass_host = node and the port is not standard, so that we can solve the problem in apache/apisix#6296 in a better way when:

1. the port in the Host header is checked
2. multiple nodes which have different host name

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

local t = love.thread.newThread([[
error()
]])
t:start()

The above code doesn't show default love.threaderror as expected (or a custom set love.threaderror). Not a massive bug - but something to be aware of if no error message is given

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.