UPYUN's open source software for OpenResty development
UPYUN's open source software for OpenResty development.
OpenResty is a full-fledged web platform by integrating the standard Nginx core, LuaJIT, many carefully written Lua libraries, lots of high quality 3rd-party Nginx modules, and most of their external dependencies. It is designed to help developers easily build scalable web applications, web services, and dynamic web gateways.
Slardar is a HTTP load balancer based on Nginx and lua-nginx-module, by which you can update your upstream list and run lua scripts without reloading Nginx.
This module allows for on-the-fly base64 encode. As same as the standard ngx_http_gzip_module.
Nginx module for the Zstandard compression.
Manage Nginx upstreams in pure ngx_lua.
Lua HTTP client cosocket driver for OpenResty / ngx_lua, interfaces are more flexible.
This lua library is a request processing rate limit module for ngx_lua. It is used to limit the request processing rate per a defined key between multiple NGINX instances. The limitation is done using the "leaky bucket" method.
This lua-resty library help you to synchronize data(from redis, mysql, memcached and so on) based on the version changes.
It will check the freshness by comparing the version cached by itself(stored in shared memory) and the one from your external suits, data will be updated when the cached one is stale or for the first time.
ngx.ctx
is a magic table provided by ngx_lua, it can be used to store per-request Lua context data, however the lifetime is limited to the current location.
See this issue for the details.
This lua-resty library can help you to bypass this limitation, i.e. it stashes and applies the old ngx.ctx
for avoiding being destoried after Nginx internal redirect happens.
This Lua library can help OpenResty/ngx_lua users to load config from consul.
This Lua library can help OpenResty/ngx_lua users to dynamically load lua files/scripts.
Yet Another HTTP library for OpenResty.
Lua module for limiting request rate for OpenResty/ngx_lua, using the "token bucket" method.
The semantic of If-Range isn't implemented correctly when using nginx's slice module.
See here for the details.
The autoindex module doesn't discard the request body explicitly,
hence request body will be treated as a pipelined request, and most of time
another unexpected response will be sent to client.
See here for the details.
When the header delimiter is \n
(rather than \r\n
),
ngx.req.raw_header
cannot get the complete protocol headers in some case.
See here for the details.
some ngx_lua's APIs(like ngx.flush
) don't handle the nginx filter finalize correctly,
thus the Lua VM may raise some exceptions.
See here for the details.
When the SSL/TLS handshake reuses a existing session and the connection upgrades to HTTP/2, segmentation fault might occur when SSL/TLS renegotiation happens.
This problem only happens under the specific Nginx and OpenSSL combinations.
See here for the details.