Kong : parameter support in url

[thibaultcha]

Hi, and welcome!

The best resource on this topic if you are just getting started is the Proxy Guide:

https://docs.konghq.com/1.1.x/proxy/

Long story short, Kong doesn’t have to know about the dynamic segments in your URL path component. Specifying a prefix (e.g. /lead) will work just fine. Most likely, your API will return HTTP 404 in the event than a request hits a non-existing path (e.g. /lead/foo).

If you’d rather enforce that Kong can only proxy those two paths, then a regex path is your goto choice (also documented in the above resource). You can leverage regex capture groups to extract the value of those path segments. Have a look at this post for an in-depth dive into regex paths and capture groups:

A few words on regex URIs usage and common pitfalls

After recently discussing about regex URI usage and gotchas with some of our users and customers, it was brought to our attention that our documentation on the subject was rather sparse… Until we improve it, my coworker @Cooper suggested that a wrap-up about regex URIs be made public here, so that you can make the best usage of this awesome feature! So here we go: a few words on recommended practices, pitfalls and upcoming improvements to regex URIs. Refresher The Kong API entity (configurable…