In the console, it looks that the mapping is right :
[2021-09-25T12:45:09.646Z] INFO micro1-497396/API: ♻ Generate aliases for '/' route...
[2021-09-25T12:45:09.649Z] INFO micro1-497396/API: GET /test/fixed/:param1/:param2 => test.func2
[2021-09-25T12:45:09.649Z] INFO micro1-497396/API: GET /test/:param1/:param2/:param3/:param4? => test.func1
But when calling:
[2021-09-25T12:45:14.131Z] INFO micro1-497396/API: => GET /test/fixed/param1/param2
[2021-09-25T12:45:14.132Z] DEBUG micro1-497396/API: Alias: GET /test/:param1/:param2/:param3/:param4? => test.func1
[2021-09-25T12:45:14.133Z] INFO micro1-497396/API: Call 'test.func1' action`
whenever a GET /test/fixed/param1/param2 is issued, func1 is hit instead of func2
Same happens if parameters is passed instead of REST and autoAlias is set to off and manual aliases are inserted in the apigw.
Consider the following code:
API GW:
Service:
In the console, it looks that the mapping is right :
But when calling:
whenever a GET /test/fixed/param1/param2 is issued, func1 is hit instead of func2 Same happens if parameters is passed instead of REST and autoAlias is set to off and manual aliases are inserted in the apigw.
Any suggestions ?