Swagger 2.0 Prioritization?

24 Views Asked by At

We're currently using Swagger 2.0 as our YAML configuration.

Let's say, I have these two paths:

Path A - accepts path parameter

GET https://my-gateway.com/client/{client-id}

Path B:

POST https://my-gateway.com/client/addNewClient

As a tester, I want to verify my gateway returns correct error messages on Path B:

I want to produce - 404 Error Not Found

Test request:

POST https://my-gateway.com/client/addNewClientzzz

I'm receiving 405 instead of 404, possibly because it falls under Path A, and treats 'addNewClientzzz' as {client-id} (path parameter).

Just wondering if this is an expected behavior? Does it check first the path, and not the method?

Currently reading GCP API Gateway and OAS Documentations.

0

There are 0 best solutions below