@shreemaan-abhishek lint issue

I tested this change and it doesn't seem to work for %2F (encoded slash or solidus /)...

In my opinion we should add more test cases for different special characters. I ran some local test on a subset of URL-encoded special characters with api7/lua-resty-radixtree v2.9.1 and v2.9.2 and that's what I got:

%2F (/) appears to be the only character that still breaks the radixtree parser 🤔

@mikyll, this is expected behaviour as / is a delimiter for urls. If / is allowed as a special character, there will be no regularity in the boundary of the url parameter. Consider the following example:

route uri: /v1/:id/products/:type/list
request uri: /v1/123/products/footwear/list

If / is also accepted as a special character then the id url parameter would be incorrectly evaluated to 123/products/footwear/list.

@shreemaan-abhishek thank you for the reply, but I think you misunderstand my previous comment... I agree that / should only be treated as a path separator, it wouldn't make sense otherwise and it would also lead to security issues.
However, that's exactly the reason why we need URL-encoding: when we URL-encode ("percent-encoding") characters, they are treated as raw data.

Currently, APISIX with radixtree_uri_with_parameter doesn't fully support this, since the router fails to route requests that contain %2F in a path parameter and returns 404: Not Found.

This PR fixed the problem for many special characters but not for %2F (encoded /)!
See the comparison table above.

Please see issue #11810 for further information.