resource-filtering policy does not work with debug mode

[exalate-issue-sync]

Describe the bug :

In debug mode, a copy of the original API is deployed on the gateway, with a different context-path.

For instance, if an API has /foo as context-path, the debug mode will deploy a "debuggable API" with context-path /6b1648e5-621a-4b4c-9648-e5621acb4ccc-foo

The root cause is that the v4 engine does not provide the same execution context as the v3 to the resource filtering policy.

In V3, the policy receive both the original context-path /foo and the debug one /6b1648e5-621a-4b4c-9648-e5621acb4ccc-foo, and the pattern matching can work with the original path.

In V4 emulation engine, the policy receive only the debug one /6b1648e5-621a-4b4c-9648-e5621acb4ccc-foo, and the pattern matching can't work.

Desktop :

• Environment: [4.0.8]

• Please see Zendesk Support tab for further comments and attachments.

[exalate-issue-sync]

This issue has been fixed in versions 4.2.0, 4.1.1, 4.0.10