lua-resty-radixtree
lua-resty-radixtree copied to clipboard
api7
Adaptive Radix Trees implemented in Lua / LuaJIT
Function`radix_tree_prev` in `easy_rax.c` iterates through all nodes with a lexicographic order less than `path`. May I know why?This caused a time complexity of O(N). When there are a lot of...
Does it follow longest prefix match rule ? Eg: route1 is /test/aa/* route2 is /test/aa/cc/dd So what's the match result ? @spacewander
my route host is engine*.cacazhu.com , Can support begin xxx*.xxx.com?
与院生进行初步聊了下： 需要init、set、del操作，init已经实现（new） 另一个是，这个改动点比较零散，需要细心一些，避免遗漏
Now there are only test cases, no detailed instructions and usage examples for the nginx parameters supported by var
original issue: https://github.com/apache/apisix/issues/2058#issue-678943008 For the "*" syntax, my understanding is that "*action" is an optional parameter. For example if we configure "uri": "/:id/foo/*action/bar" in APISIX, both requests "/1/foo/get/bar" and "/2/foo/bar"...
``` content_by_lua_block { local opts = {host = "127.0.0.1"} local radix = require("resty.radixtree") local rx = radix.new({ { paths = {"/aa*"}, hosts = "127.0.0.1:9080", handler = function (ctx) ngx.say("pass") end...
This PR is a spin-off from https://github.com/api7/lua-resty-radixtree/pull/141 as the implementation differs a lot but causes the same effect.
ref: https://github.com/apache/apisix/issues/10531 https://github.com/apache/apisix/issues/10531#issuecomment-1822317796
