I found a bug, it got an error when match var and have no uri args.
the test case like this.

    location /t {
        content_by_lua_block {
            local radix = require("resty.radixtree")
            local rx = radix.new({
                {
                    paths = "/aa",
                    metadata = "metadata /aa",
                    vars = {
                        {"arg_k", ">", 10},
                    },
                }
            })

            ngx.say(rx:match("/aa", {vars = {}}))
        }
    }

Hello everyone,

I've read the lua-resty-radix source code. There's no method to delete a node in a radixtree. Could anyone help me how to delete the node, please?

the lua-resty-expr had released version v1.1.0, I think we need to release a new version of lua-resty-radixtree.

@Firstsawyou what do you think?

/user/xiangnan should route to /user/:user

    local radix = require("resty.radixtree")
    local rx = radix.new({
      {paths = "/user/:user/age/:age", metadata = "/user/:user/age/:age"},
      {paths = "/user/:user", metadata = "/user/:user"}
    })
    ngx.say(rx:match("/user/xiangnan"))
    ngx.say(rx:match("/user/xiangnan/age/26"))
    assert(rx:match("/user/xiangnan") == rx:match("/user/xiangnan/age/26"))

we can take a look at this commit:

apache/apisix@5cde5ae

to fix: #107

local radix = require("resty.radixtree")
local rx = radix.new({
   {
        paths = {"/aa/*"},
        metadata = "metadata /aa",
        hosts = {"*.bar.com"}
    },
    {
        paths = {"/aa/*"},
        metadata = "metadata /aa1",
        hosts = {"*.qq.bar.com"}
    }
})
ngx.say(rx:match("/aa/bb", {host = "1.qq.bar.com"}))

this code will output metadata /aa not metadata /aa1 as we expected

dev-env: OSX
run-env: docker (which image is openresty/openresty:lastest)

when i installed lua-resty-radixtree in OSX, it would make librestyradixtree.dylib,
but the openresty/openresty:lastest image is based on debian OS, it should required librestyradixtree.so which was not make in install step

the error follow below

openresty    | tried above paths but can not load librestyradixtree.so

any idea fix this typo in friendly. just not like exec install command in docker containers.

I use RUN luarocks install lua-resty-radixtree 2.8.1-0 in the Dockerfile to install lua-resty-radixtree, but today the build process reports following error message and build failed.

Same issue here for the reference:
leafo/gifine#27

 > [27/28] RUN luarocks install lua-resty-radixtree 2.8.1-0:
#31 1.023 Installing https://luarocks.org/lua-resty-radixtree-2.8.1-0.src.rock
#31 1.654 Missing dependencies for lua-resty-radixtree 2.8.1-0:
#31 1.654    lua-resty-expr 1.3.0 (not installed)
#31 1.654
#31 1.654 lua-resty-radixtree 2.8.1-0 depends on lua-resty-ipmatcher (0.6-0 installed)
#31 1.654 lua-resty-radixtree 2.8.1-0 depends on lua-resty-expr 1.3.0 (not installed)
#31 1.654 Installing https://luarocks.org/lua-resty-expr-1.3.0-0.rockspec
#31 1.665 Cloning into 'lua-resty-expr'...
#31 2.254 fatal: remote error:
#31 2.254   The unauthenticated git protocol on port 9418 is no longer supported.
#31 2.254 Please see https://github.blog/2021-09-01-improving-git-protocol-security-github/ for more information.
#31 2.259
#31 2.259 Error: Failed installing dependency: https://luarocks.org/lua-resty-expr-1.3.0-0.rockspec - Failed cloning git repository.
------
failed to solve: rpc error: code = Unknown desc = executor failed running [/bin/sh -c luarocks install lua-resty-radixtree 2.8.1-0]: exit code: 1
make: *** [local_build] Error 17

this commit d8fc176, ci did not run

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

I am trying to match only the host with wildcard name, no paths, methods required, how to do this with package, is there any alternative method that can be used.

Omission tag v1.3

当我在mingw环境下编译lua-resty-radixtree时，我发现只要去掉easy_rax.c文件中的以下引用就可以编译通过。

...
#include <netinet/in.h>
#include <arpa/inet.h>
...

那请问引入这两个库的用途是什么呢，除了在 lua-resty-ipmatcher 这里发现有利用ffi动态加载了这两个库的方法，还有其他地方有用到么？

"vars": [
        {"arg_id", "%", "7", "<=", 4}
    ]

it means: ngx.var.arg_id % 7 <= 4,

Now we use ':' to indicate a param name like this: https://github.com/api7/lua-resty-radixtree#parameters-in-path
However, ":" is legal in uri and is recommended to indicate a custom HTTP method in RESTful API, for example, in Google's https://cloud.google.com/apis/design/custom_methods.

local radix = require("resty.radixtree")
local rx = radix.new({
   {
        paths = {"/aa/*"},
        metadata = "metadata /aa",
    },
    {
        paths = {"/aa/*"},
        metadata = "metadata /aa1",
        hosts = {"*.bar.com"}
    }
})
ngx.say(rx:match("/aa/bb", {host = "qqq.bar.com"}))

this code will output metadata /aa not metadata /aa1 as we expected

With the following two conditions met:

• opts.method matched routr.methods
• opts.matched = {}

the route match will fail.

case references: apache/apisix#1574

bug causes

https://zhuanlan.zhihu.com/p/680286939

这个是真的吗？为什么这么缺德？

Functionradix_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 routes and can't hit exactly, it performs poor.

https://github.com/api7/lua-resty-radixtree/actions/runs/7352737140/job/20191485091

Expected result, the second routing rule matches first.

{
    {
        paths = {"/aa*"},
        metadata = "metadata /aa",
        priority = 0
    },
    {
        paths = {"/aa*"},
        metadata = "metadata /aa",
        hosts = {"foo.com"},
        priority = 100
    }
}

Now there are only test cases, no detailed instructions and usage examples for the nginx parameters supported by var

如题

e.g:

bad styles:

if type(r_v) == "table" then
    for _, v in ipairs(r_v) do
        if v == l_v then
             return true
        end
     end
end

 return false

good styles:

if type(r_v) ~= "table" then
    return false
end

for _, v in ipairs(r_v) do
     if v == l_v then
          return true
     end
end

当我更新apisix-dashboard的schema.json时遇到了下面的问题，lua: ./apisix/admin/init.lua:19: module 'resty.radixtree' not found：

When I update theapisix-dashboard schema.json I met the following problems when I was working,lua: ./apisix/admin/init.lua:19: module 'resty.radixtree' not found:

于是我安装lua-resty-radixtree，但又遇到了下面的问题：

So I installed lua-resty-radixtree, but I encountered the following problem:

Hello!

I hope you are doing well!

We are a security research team. Our tool automatically detected a vulnerability in this repository. We want to disclose it responsibly. GitHub has a feature called Private vulnerability reporting, which enables security research to privately disclose a vulnerability. Unfortunately, it is not enabled for this repository.

Can you enable it, so that we can report it?

Thanks in advance!

PS: you can read about how to enable private vulnerability reporting here: https://docs.github.com/en/code-security/security-advisories/repository-security-advisories/configuring-private-vulnerability-reporting-for-a-repository

env:
os: CentOS Linux release 7.6.1810 (Core)
nginx version: openresty/1.15.8.1
built by gcc 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC)
built with OpenSSL 1.0.2k-fips 26 Jan 2017
TLS SNI support enabled

nginx.conf :

location / {
root html;
index index.html index.htm;
content_by_lua_block {
local radix = require("resty.radixtree")
local rx = radix.new({
{
path = "/aa",
metadata = "metadata /aa",
host = "foo.com",
method = {"GET", "POST"},
remote_addr = "0.0.0.0",
},
{
path = "/bb*",
metadata = "metadata /bb",
host = {"*.bar.com", "gloo.com"},
method = {"GET", "POST", "PUT"},
remote_addr = "fe80:fe80::/64",
}
})

            ngx.say(rx:match("/aa", {host = ngx.var.host,
                                     method = ngx.req.get_method,
                                     remote_addr = ngx.var.remote_addr}))
        }
    }

error.log
radixtree.lua:338: bad argument #2 to 'band' (number expected, got nil)
stack traceback:
coroutine 0:
[C]: in function 'band'
lualib/resty/radixtree.lua:338: in function 'match_route_opts'
lualib/resty/radixtree.lua:414: in function 'match_route'
lualib/resty/radixtree.lua:474: in function 'match'

test:
curl 127.0.0.1/aa

nginx worker exit while run radixtree test
The error message is as follows
2021/01/26 04:15:41 [alert] 10469#10469: worker process 10470 exited on signal 11

nginx.conf example :

server {
listen 127.0.0.1:80;

  location /test {
        content_by_lua_block {
                local radix = require("resty.radixtree")
                local route_count = 1000 * 100
                local match_times = 1000 * 1000 * 10
                
                local routes = {}
                for i = 1, route_count do
                    routes[i] = {paths = {"/user" .. i .. "/:name"}, metadata = i}
                end
                
                local rx = radix.new(routes)
                ngx.update_time()
                local start_time = ngx.now()
                
                local res
                local path = "/user500/gordon"
                for _ = 1, match_times do
                    res = rx:match(path)
                end
                
                ngx.update_time()
                local used_time = ngx.now() - start_time
                ngx.say("matched res: ", res)
                ngx.say("route count: ", route_count)
                ngx.say("match times: ", match_times)
                ngx.say("time used  : ", used_time, " sec")
                ngx.say("QPS        : ", math.floor(match_times / used_time))
                ngx.say("each time  : ", used_time * 1000 * 1000 / match_times, " ns")
        }
 }

}

Recurrence request ：
curl http://127.0.0.1:80/test -v

more err message :
10489#10489: *4 lua entry thread aborted: runtime error: /usr/local/nginx/lua/resty/radixtree.lua:418: missing declaration for symbol 'free'

fix commit ： master...jfboys:fix-free-fail

when there are multiple URIs, need to record which matches the current request.

we can use _uri to store the path of router.

{
                paths = {"/aa", "/bb*", "/name/:name/*other"},
                hosts = {"*.bar.com", "foo.com"},
                methods = {"GET", "POST", "PUT"},
                remote_addrs = {"127.0.0.1","192.168.0.0/16",
                                "::1", "fe80::/32"},
                vars = {
                    {"arg_name", "==", "json"},
                    {"arg_weight", ">", 10},
                },
                filter_fun = function(vars, opts)
                    return vars["arg_name"] == "json"
                end,

                metadata = "metadata /bb",
            }

ngx.say("matched uri: ", opts.matched._uri)
ngx.say("matched host: ", opts.matched._host)
ngx.say("matched method: ", opts.matched._method)

In some scenario, we need set a condition like arg_id in (1,3,4) to match the routes .

I think it's good to have a operator IN

hi api7team,
I tested and found radixtree.new() cost nearly 120s when uri_routes num is 10w (32core, 32G, centos Physical Machine server)，
I use radixtree_uri_with_parameter for http router.
do you have any optimize suggestions?

apache/apisix#841,
Many times we need to specify a certain batch of users as grayscale users

vars = {
    {"arg_name", "in", ["lua","java","c"]}
}

support to parse parameters in path, I am learning the gin project:

https://github.com/gin-gonic/gin#parameters-in-path

my route host is engine*.cacazhu.com , Can support begin xxx*.xxx.com?

ref:
apache/apisix#10531
apache/apisix#10531 (comment)

Original issue:

apache/apisix#2750

For example:
https://docs.mongodb.com/manual/tutorial/query-documents/

original issue: apache/apisix#2058 (comment)

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" should be matched by the route, while request "/3/foo/a/b/bar" should be rejected. However in APISIX the "" syntax has similar behavior with the colon syntax. The tests 7, 8 here https://github.com/api7/lua-resty-radixtree/blob/master/t/parameter.t seems broken: they are named "/name/*name/foo" but tested with "/name/:name/foo"

I want to get path parameters in apisix control api , the route default call dispatch method ,but can not get path param in the customer control api

according doc ， if the end of the path is , it means that this is a prefix path. most cases do it well，but path ， like //ping* , dont. it matches /xxx/ping , /xxx/ping , /xxx/pinggggg , /xxx/xxx/ping and so on. but it dont match some cases, like /xxx/pingxxx (x is not g) , /xxx/ping/xxx

与院生进行初步聊了下：
需要init、set、del操作，init已经实现（new）
另一个是，这个改动点比较零散，需要细心一些，避免遗漏

Since the lua-resty-expr lib released v1.2.0 version, any plan update to the new version? We are eager to use the new feature.

local rx = radix.new({
{
path = "/aa",
metadata = "metadata /aa",
host = "foo.com",
method = {"GET", "POST"},
remote_addr = "127.0.0.1",
}
remote_addr is string type
remote_addr config like this remote_addr = {"192.168.10.0/24", "192.168.20.0/24"， “192.168.50.1”，“192.168.50.2”,}
suport multiple VLAN and ip ;