KB Article #163475
Rules for matching relative paths
The Gateway's relative path uses the longest match when matching a relative path to a policy.
The path /healthcheck2 and /healthcheck/a will match to a relative path /healthcheck if /healthcheck2 and /healthcheck/a don't exist.
If there is no match the path of / will be called, which in the Default Services maps to a policy returning "403 Access Denied" back to the client.
In order to perform exact matching of a path you would need to use the Resolver->Relative Path filter in a policy. This filter has configuration input of a filter name and a relative path which accepts a regular expression.
For example, enter ^/services/helloService$ to exactly match a path with a value of /services/helloService. Incoming messages received on a matching relative path value are passed on to the next filter on the success path in the policy.