I’m trying to enable exact matching on the key_detail endpoint and I’m running into issues.
I’ve tried enabling the following settings in the tyk.config file:
“enable_path_prefix_matching”: true,
“enable_path_suffix_matching”: true,
“enable_strict_routes”: true
None of the options seem to be working. The default fuzzy matching is frustrating when 12345 and 123456 both return the same record despite there being two DISTINCT records.
The URL matching controls that you’re trying to use are applied to the router within the Tyk Gateway when an request is received to an API proxy you have deployed on the Gateway (i.e. where you have created an API definition and loaded this to the Gateway).
Please refer to the documentation here: URL Path Matching
These controls are not applied to the Tyk Gateway’s management/control API; I’m sorry for the confusion.
Kind regards,
Andy.
Hey @Andy_O!
Always love meeting another Andy/Andrew, especially with style.
So if I understand what you’re saying the strict pattern matching is only applied on deployed proxies we’ve set up, not on default Tyk Gateway endpoints?
The path I’m seeing the fuzzy match on is from the management.control API specifically the GET /tyk/keys/{keyID}. When fetching keys 12345 and 123456 they both return the same record despite there being two separate records.
Is there some way for us to turn off fuzzy match on the management/control API?