Thanks for you pr :), just wait for others preview.

nice PR

solve above

describe a strange phenomenon, I was using /route_status api and create new routes because I found that using route id 1 and /hello always failed when I ran my local test cases, even through other test cases, like

$prove -I../test-nginx/lib -I./ -r -s t/router/radixtree-host-uri.t         
t/router/radixtree-host-uri.t .. 10/? 
#   Failed test 'TEST 5: hit routes - status code ok'
#   at /usr/local/apisix/../test-nginx/lib/Test/Nginx/Socket.pm line 948.
#          got: '404'
#     expected: '200'

#   Failed test 'TEST 5: hit routes - response_body - response is expected (repeated req 0, req 0)'
#   at /usr/local/apisix/../test-nginx/lib/Test/Nginx/Socket.pm line 1589.
#          got: '{"error_msg":"404 Route Not Found"}
# '
#     expected: 'hello world
# '

#   Failed test 'TEST 6: hit routes - status code ok'
#   at /usr/local/apisix/../test-nginx/lib/Test/Nginx/Socket.pm line 948.
#          got: '404'
#     expected: '200'

#   Failed test 'TEST 6: hit routes - response_body - response is expected (repeated req 0, req 0)'
#   at /usr/local/apisix/../test-nginx/lib/Test/Nginx/Socket.pm line 1589.
#          got: '{"error_msg":"404 Route Not Found"}
# '
#     expected: 'hello world
# '

until I debugged at

when run test, the user_routes.values is nil, but when start apisix, it work.

after find this exception, something change, run the test case is back to normal, and cannot be reproduced. >_<|||

is it necessary to add a case：
create a route disabled -> hit route failed-> enable it -> hit route successfully?

describe a strange phenomenon, I was using /route_status api and create new routes because I found that using route id 1 and /hello always failed when I ran my local test cases, even through other test cases, like

$prove -I../test-nginx/lib -I./ -r -s t/router/radixtree-host-uri.t         
t/router/radixtree-host-uri.t .. 10/? 
#   Failed test 'TEST 5: hit routes - status code ok'
#   at /usr/local/apisix/../test-nginx/lib/Test/Nginx/Socket.pm line 948.
#          got: '404'
#     expected: '200'

#   Failed test 'TEST 5: hit routes - response_body - response is expected (repeated req 0, req 0)'
#   at /usr/local/apisix/../test-nginx/lib/Test/Nginx/Socket.pm line 1589.
#          got: '{"error_msg":"404 Route Not Found"}
# '
#     expected: 'hello world
# '

#   Failed test 'TEST 6: hit routes - status code ok'
#   at /usr/local/apisix/../test-nginx/lib/Test/Nginx/Socket.pm line 948.
#          got: '404'
#     expected: '200'

#   Failed test 'TEST 6: hit routes - response_body - response is expected (repeated req 0, req 0)'
#   at /usr/local/apisix/../test-nginx/lib/Test/Nginx/Socket.pm line 1589.
#          got: '{"error_msg":"404 Route Not Found"}
# '
#     expected: 'hello world
# '

until I debugged at

apisix/apisix/http/router/radixtree_uri.lua

Line 85 in 9e3c34a

create_radixtree_router(user_routes.values)

when run test, the user_routes.values is nil, but when start apisix, it work.

after find this exception, something change, run the test case is back to normal, and cannot be reproduced. >_<|||

If this magical event happened next, you may cc
@membphis @spacewander @tokers for help😊

is it necessary to add a case：
create a route disabled -> hit route failed-> enable it -> hit route successfully?

test case 1 ~ 4 is testing for uri match, the order is
create a route enable(default) -> hit route successfully-> disable it -> hit route fail

test case 5 ~ 8 is testing for host + uri match, the order is same as above.

I think combining these four steps into one test case would have the same effect.

thanks to the people at code review, and thanks for the guidance!