stream-lua-nginx-module icon indicating copy to clipboard operation
stream-lua-nginx-module copied to clipboard

Embed the power of Lua into NGINX TCP/UDP servers

Results 47 stream-lua-nginx-module issues
Sort by recently updated
recently updated
newest added

https://github.com/openresty/stream-lua-nginx-module/blob/65567d19042ac809ed1f75708e2b2e47f718d1ef/src/ngx_stream_lua_output.c#L78 maybe add this behavior in the document and why?.

I am using OpenResty as a TCP (stream) proxy. I have been capable to read TCP packets using `reqsock:peek` and `preread_by_lua_block` directives. However, would like to change certain bytes of...

Example taken from https://github.com/openresty/stream-lua-nginx-module#reqsockpeek ``` local sock = assert(ngx.req.socket()) local data = assert(sock:peek(1)) -- peek the first 1 byte that contains the length data = string.byte(data) data = assert(sock:peek(data +...

Using the example provided for the `peek` API for a UDP stream, within the `preread_by_lua_block`, gives the error: `Attempt to call method 'peek' (a nil value)` Is it possible to...

Hello Dears, Could anyone help me? I test it with a TCP client. the preread method is not called until the fifth byte is sent. Why? The interactive message information...

I have tried to set the socket to accept data bytes in both pre and content phases_ Received is always 0?

When I use init in the stream module_ by_ lua_ Block and init_ worker_ by_ When blocking, my nginx can't open the child process. Why??? And also reported a mistake...

I add 2 preread handler, first it runs lua preread handler, but lua preread handler return NGX_OK when finised. the problem is that the seconed preread handler is not called

https://github.com/openresty/stream-lua-nginx-module/blob/1a1e49bd4be0f858818c4f133a06e2ac9a2ab306/src/ngx_stream_lua_module.c#L790 The macro NGX_STREAM_SSL in the wrong place

Hello, I'm trying to use openresty as a udp server. But some packets were lost. Centos7 nginx version: openresty/1.17.8.2 1. tcpdump: openresty received 3 packets, but only responded once ```...