A distinguishing feature of APISIX from other API gateways is that it allows users to choose different routers to better match free services, making the best choice between performance and freedom.
Set the route that best suits your business needs in the local configuration
apisix.router.http: HTTP Request Route。
radixtree_uri: (Default) only use
urias the primary index. Support for full and deep prefix matching based on the
radixtreeengine, see How to use router-radixtree.
Absolute match: Complete match for the given
uri, such as
Prefix match: Use
*at the end to represent the given
urias a prefix match. For example,
match priority: first try absolute match, if you can't hit absolute match, try prefix match.
Any filter attribute: Allows you to specify any Nginx built-in variable as a filter, such as URL request parameters, request headers, cookies, and so on.
radixtree_uribut also support parameter match.
host + urias the primary index (based on the
radixtreeengine), matching both host and URL for the current request.
apisix.router.ssl: SSL loads the matching route.
radixtree_sni: (Default) Use
SNI(Server Name Indication) as the primary index (based on the radixtree engine).