Resource Path "/" subpaths proxies not working

Google Cloud Apigee
1

Hi,

I have created a proxy with base path: /api/v1/comms/partners
And in the product i have defined the resource path to be “/”. so that all sub paths are supported.
Now, my problem is that i have 4 requests for this proxy

  1. GET with path: /api/v1/comms/partners, It has VerifyAccessToken and a AssignMessagePoilcy, and all works fine
  2. POST with path: /api/v1/comms/partners, It has VerifyAccessToken and a AssignMessagePoilcy, and all works fine
  3. DELETE with path: /api/v1/comms/partners, It has VerifyAccessToken and a AssignMessagePoilcy, and all works fine
  4. PUT: with path: /api/v1/comms/partners/{partnerId}/providers/{providerid}, It has VerifyAccessToken and a AssignMessagePoilcy too, but it never calls these policies. The request is passing successfully without even checking the access token and assign message policy. The call is passed even if i do not send the access token at all.
    Below is how i have set them up:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> request.verb == "OPTIONS" verify-oauth-v2-access-token Assign-Message-UserInfo remove-header-authorization (proxy.pathsuffix MatchesPath "/") and (request.verb = "GET") Get PUT calls verify-oauth-v2-access-token Assign-Message-UserInfo remove-header-authorization (proxy.pathsuffix MatchesPath "/") and (request.verb = "PUT") Get POST calls verify-oauth-v2-access-token remove-header-authorization Assign-Message-UserInfo (proxy.pathsuffix MatchesPath "/") and (request.verb = "POST") Get DELETE calls verify-oauth-v2-access-token Assign-Message-UserInfo remove-header-authorization (proxy.pathsuffix MatchesPath "/") and (request.verb = "DELETE") /api/v1/comms/partners default secure default

What is it that I am missing for the PUT request to check the policies attached?

Thanks,

Kumud

2

@Kumud Gautam

Try with the below changes as mention

<Condition>(proxy.pathsuffix MatchesPath "/*") and (request.verb = "PUT")</Condition>
3

Adding “/*” in condition does not work. It fails the base API itself.