A distinguishing feature of Apache APISIX from other API gateways is that it allows you to choose different Routers to better match free services, giving you the best choices for performance and freedom.
You can set the Router that best suits your needs in your configuration file (conf/config.yaml).
Set the route that best suits your business needs in the local configuration
It can have the following configurations:
apisix.router.http: The HTTP request route. It can take the following values:
radixtree_uri: (Default) Only use the
urias the primary index. To learn more about the support for full and deep prefix matching, check How to use router-radixtree.
Absolute match: Match completely with the given
Prefix match: Match with the given prefix. Use
*to represent the given
urifor prefix matching. For example,
/foo*can match with
match priority: First try an absolute match, if it didn't match, try prefix matching.
Any filter attribute: Allows you to specify any Nginx built-in variable as a filter, such as URL request parameters, request headers, and cookies.
radixtree_uribut also supports parameter match.
radixtree_host_uri: Matches both host and URI of the request. Use
host + urias the primary index (based on the
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).