URL Path Matching - Listen Path - Regex

Product
,
1

I upgraded my TYK open source api gateway from version 5.0.0 to 5.3.7 LTS.
However, my previously working apis with similar listen_path started redirecting to wrong targets.
Requests that I send API2 are constantly going to API1.

API1 listen_path :

"proxy": {
    "listen_path": "/abc-def/web/",
    "target_url": "https://www.abc.com",
    "strip_listen_path": false
},

API2 listen_path :

"proxy": {
    "listen_path": "/abc-def/public/xyz/",
    "target_url": "https://www.abc.com",
    "strip_listen_path": false
},

I tried using both control characters (^ and $) in listen_path but could not get an exact match. ( ^/json$ )

I added the following variables to the tyk.conf file but it did not work:
“http_server_options”: {
“enable_path_prefix_matching”: true,
“enable_path_suffix_matching”: true,
“enable_strict_routes”: true,
…

My only wish is to be able to use it by making an exact match in listen_path like the old version, but it doesn’t work.

2

Hi mmgul,

I suspect the issue might be similar to this API Priority in tyk-gateway 5.3.2 . However, could you share the full API definitions for us to test?